Have a look at elements. And you'll find that, no matter how insignificant, creating a separate model buys you much ease of use.
On Sun, May 3, 2009 at 7:04 AM, Rangi <rangi...@gmail.com> wrote: > > In the blog-style MVC examples, you have one model (eg. "post"), a > controller with actions like "write", "view" and "list", and views for > each action. This is all quite easy to understand and works really > well. > > What about more complex pages, such as the Yahoo Homepage, or the > Facebook Homepage or Profile page? They involve loads of different > data sources (eg. news, people, photos, videos, comments, etc) and > dont seem to neatly map to single models and controllers like the > simple blog-style examples. > > Any advise on how best to create complex pages like these using > CakePHP would be much appreciated. > > Cheers, > Rangi > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
