Requesting your experience, comments, insight, etc. on CakePHP, thanks. (BTW, you can go into details, I'm not a 16 year old copypasta script kiddie.)
In that case, maybe you could also make a proper introduction of the subject. I'm pretty sure a lot of people have no idea what you're talking about, but would be interested if they did.
It's a PHP framework similar to Ruby on Rails. http://phpcake.org/
Sorry, wrong link, http://cakephp.org/ is what I meant.
>>2
Sorry. Yeah, it's an idiomatic port of Ruby on Rails for PHP (a MVC-based framework for rapid web applications development). It looks pretty good and pretty clean, and I would like to hear Anonymous' experience if he/she has worked with it for a long time.
I've actually looked through the code of it, and there are parts of it that I find a tad excessive. Live if you name your model "Tags" then it will automatically associate it with a controller class called "TagController" and it will associate it with a particular 'tag' table in the db... But all of this is done through functions that try to 'singularize' a plural word, or 'pluralize' a singular word.
I think this is a little much to run through in a webapp. If it was something that was run through just once, that's fine. But this is run through a lot. I don't like this trade-off of inefficiency in order to make things easier.
Wow. Someone thought that was actually a good idea when they wrote that?
Meh.
>>6
Yeah, I noticed that when I tried it. I thought it was silly (I would just calle everything Tag), but overall acceptable. After all, if you're in for maximum performance, don't use a framework. (That's not to say let's waste it happily, but these are small, relatively inoffensive functions.)
>>8
The problem is that the functions change between singular and plural running an array of RegEx strings through preg_* functions.
They do a good job of allowing you to customize things. Some of the classes have empty functions that are Before<action> After<action> which are called before and after an action. So you can overload them in a sub-class if you need something to happen before or after a delete is preformed, for example.
cake.jar
is a lie .. is a lie .. is a lie ..