On 23/05/12 14:16, hill180 wrote:
There might be a bit of a misunderstanding. Points were not to highlight what was better, just what Cake has. I also believe YII is a solid framework. On the documentation, I found the API docs were excellent but from a manual side "definitive guide", lacking. I'll give an example. I had to setup session to store in the DB "CDbHttpSession" API is easy to find, but on the manual side (definitive guide), there is no reference.
On Wed, May 23, 2012 at 4:00 AM, Steve Found <stephen@foundfamily.co.uk> wrote:
On 23/05/12 03:35, hill180 wrote:
Like you, I also tried Yii and came back to CakePHP. Apart from point 2 though, I do not totally agree with your points. Yii also has excellent documentation and is also a solid framework.This is not a holy war statement.
After looking at Yii, getting the two books and reading and watching a lot of the tutorials, making a small app in Yii. I think I am going to stay with Cake.
1. Cakephp's Documentation is amazing.
2. Great Community
3. Familiar with CakePHP
4. CakePHP is a solid framework.
I like Yii's Search Widgets and Ajax, but I think I would prefer doing the Ajax by hand. Don't need to worry about Composite Keys.
What are your thoughts on Yii? Tried Yii? Please be constructive.. I know this forum is bias to CakePHP, but I just want a general opinion if you tried it.
--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
I would go so far as to suggest that in comparison to Cake 1.x, Yii is probably not a comparative framework since Yii does not support PHP 4 and utilises Lazy Loading of classes which is a feature that affects Cake 1.x in respect to comparative speed ( speed is a criticism that is always levelled at Cake in addition to being 'restrictive' ). Apart from these I found the two to be remarkably similar. Both have model behaviours, both have Components, both have Plugins, both have themes, views and layouts and since Cake 2.0 cake also has lazy loading and since 2.1 also has the ability to wrap layouts in other layouts.
I do prefer the Models of Yii in that each model object represents a record and you get an object back instead of Cake's arrays ( a feature on Cake 3.0's roadmap ).
The Widgets of Yii, I both love and hate. From a developers point of view they are great since you just use it and it sorts out the Javascript you need in the header and body without you needing to worry about it. From a web designers point of view however, they are not so good. The whole point of MVC is supposed to be that web designers can work on views whilst developers sort out models and controllers. In Yii therefore, web designers need to have a detailed knowledge of Yii widgets which often require a lot of configuration to get them how you want unless you are happy with what you are given out of the box.
All in all, I do not think Cake 2.x and Yii are too far apart and each has it's strengths and weaknesses depending on your viewpoint.
--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
No comments:
Post a Comment