Mark Quinn wrote: > To me, this is where your argument breaks down. A view is only part of > the picture. > > A view *and a layout* *and perhaps some elements* is the _view_ > > To say a view cannot set data is shortsighted. Perhaps a better way to > think of this is to think of "passing" data instead of setting data.
Agreed, a "view" is more than a _view_ :) But in the concept meaning of view it does not set any data. Of course it uses/passes the data on to create itself so to say. But combining that with layouts (which I kinda lost focus on when writing the first reply) I would like to go back to the "only viewing view", emphasizing the hierarchical relation of layout and view. And in that sense I see the view on a lower level than the layout. The view as such uses helpers/elements to create its content, but I don't like the idea of letting the view set something above/outside of it. I'd rather create some logic to set layout parameters from the view-calling controller instead of making the layout view-dependent, which it would be if it accepted data set by a view. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
