On 4/18/07, beetlecube <[EMAIL PROTECTED]> wrote: > > > For those who have done PHP development for a client, and used cakePHP > to build their sites, a question: > > Have you received complaints from the client, when they have tried to > add a page on their own, ? like: > > "This cakephp stuff is complicated, and I just want to add another > page that accesses the database, and I didn't know you have to create > three different files for it. I can't get a php coder to help me, > because they don't know cakephp or MVC" > > Just curious and thought I'd ask
I'm a little bit confused. When you say "Client", you mean somebody who will be USING your CakePHP app through a browser? CakePHP is not exactly hard to learn, and in the long run makes code far more maintainable. Any half-decent PHP coder can pick up the CakePHP stuff relatively quickly and any programmer who has done a bit of OOP should know at least the basics of MVC. That comment you quoted sounds like somebody not willing to put in a bit of effort to understand why there are 3 files needed. Besides, unless you need to do data validation or some callbacks in the Model, the file is about 3 lines long. The controller maps out the different actions the user can access and the views have "what to show". Sounds sensible to me. Hope this helps. Regards, Gonzalo. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
