Ugh... Assume that the view gets everything from controller. Then this
controller is the thing that should gather everything together before
shipping it to the view. Let the template decide the form, let the
controller decide the content.
That's fair enough, but say you've got 20 possible
On Wed, 25 Apr 2007 11:58:02 +0100, Carl Johnstone wrote
> > Ugh... Assume that the view gets everything from controller. Then this
> > controller is the thing that should gather everything together before
> > shipping it to the view. Let the template decide the form, let the
> > controller
Maybe I am confused about MVC, but wouldn't you want the view to decide
how to
present what is sent to it by the controller, and hence have the
controller
handle this?
I don't know if it's you that's confused or me that's confused ;-) I can see
your point of view though.
From my point of vi
On Wed, Apr 25, 2007 at 10:41:12AM -0400, Joe Landman wrote:
> > What Steve wants is some way of being able to decide in the View
> > which of those elements are included and load them accordingly.
>
> ... and this should be done at the controller level is what I am saying. You
> can even have y
my approach in cases like this has been to have models/database
tables for the pages themselves.
- a page has_many components
- a controller queries the db for the components to display on the
page[*] and stashes the list
- the controller, now knowing which components will be displayed,
sta
