Maybe you can make a template system, whre you define in a simple way
what is the data you want and make the controller fetch it from the
models and handle it to a view.
+-- (is really a special model)
/
ReportTemplate ---> | Reports |
Models ---------------->| Controller | --------> views
Could it be? Or I screwed it?
On Jun 20, 7:33 am, AD7six <[EMAIL PROTECTED]> wrote:
> On Jun 19, 1:49 pm, simon <[EMAIL PROTECTED]> wrote:
>
> > > Why isn't all of that retrieval logic in the controller? I.e. you
> > > generate all the data you want in your controller, and you simply loop
> > > on your retrieved data in the vew.
>
> > Ah, see I'm totally with you on this... I have a quite specific
> > problem though: each type of template needs a specific set of data.
>
> In my experience, specific problems that warrant breaking rules are a
> lot rarer than many think. Are you wanting your users to be able to
> edit the view files? if not, your controller calls the view files - it
> knows which view file it's going to use it should know which data it
> wants to receive; if so, why? and in any event I'd suggest designing
> towards the same answer ;).
>
> If you are still not convinced, what's the code in your controller
> method /templates/get_items_this_month/ ? specific discussions are
> more likely to give you specific answers.
>
> hth,
>
> AD
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
