Same here. Symfony is a pain to install. I still beg someone to write a detailed book on Cake.
On Jul 16, 8:29 am, "Sam Sherlock" <[EMAIL PROTECTED]> wrote: > cake installed and working in seconds flat > > symfony waded through documentation for a couple of hours with not much to > show for it > > Now, now. Let's look at the competition fairly. I think the only > > > place where Symfony has CakePHP beat is the humungous amounts of > > documentation they have vomited out. > > but still got no where with it. and managed to get things going with cake > sparse documentation > > Once you're a little way in you'll know which you prefer and can then carry > > > on the project with the framework that you feel most comfortable with. > > Small & large projects can be made with various pieces of cake. And its not > over complicated. > > Cake's documentation is sure to improve; > > On 16/07/07, Nick <[EMAIL PROTECTED]> wrote: > > > > > There are few articles on the web that compare the two frameworks from > > peoples real world experience, and those may be useful to you. Just > > search for symfony vs. cake > > > When we were exploring this, about as quickly as we recognised that > > the Zend framework was on the wrong track (less than 30 mins :), we > > found that Cake was very appealing for number of reasons. It was > > trivial to get started, which is not a great reason but an influential > > one none the less and might be important to you, it's extensible, > > promotes some good design concepts and conventions, and has many > > concepts that fitted well with our own experience - in essence, it > > felt "right". Once you've had a taste of it so to speak, you would > > probably find that there's no upside to doing anything non-trivial > > without it. > > > We've only looked at Symfony briefly and it seems much harder to get > > started, but to be fair and inevitably like most cake users, we > > haven't tried it yet as once you find something that you like, the > > search for a solution tends to stop. > > > As we explored further, we found that Cake isn't without problems, and > > it has some things that would have benefited from being done > > differently. Cake also uses arrays for representing model data, and > > this has some quite wide implications. However that area is planned > > for improvement in Cake 2.x and if you're not used to OO design then > > you might not care or even notice. On the flipside, Cake has a concept > > for use with Controllers called Components, and we threw together a > > Component that by simply referencing in a Controller, gives us the > > class based view of data that we were missing. Being able to assist or > > solve issues with a bit of code and have it applied across the board > > in seconds is appealing, and there various other neat concepts. > > > Frameworks are largely a matter of preference, and what one person > > feels happy with or considers better may be different to the next > > person. Trying both Cake and symfony for real, perhaps in parallel on > > the same real world project, may be the best way to decide. Once > > you're a little way in you'll know which you prefer and can then carry > > on the project with the framework that you feel most comfortable with. > > > Good luck! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
