On 27 Jun., 23:19, Fabien POTENCIER <[EMAIL PROTECTED]>
wrote:
> The View system is also one of the sub-framework I want to refactor for
> 1.1 or 1.2. I want to create 2 distinct layers: a view layer and a
> template layer. This distinction will allow easier integration of
> templating systems like phptal or smarty. The link between the view and
> the template will be done via a new sfTemplateContext object. This
> object will hold all the variables to be passed to the template
> (instance variables from the action or the global ones created by sfView
> - sf_*). It will allow the developer to inject some global variables
> into the template context and to use the templating system for partial
> without initializing a new view object (so, it will be much faster).
> This object will also holds the helper objects... Yes, I also want to
> convert helpers to classes (This is one of oldest design changes we
> discussed here on the ML).
Hi Fabien,
do you work on these things next time?
Do you think you can even completely decouple action from the view?
I mean what I would like to see is to not rely on the last entry of
the action stack.
I think this is required for "pages" with several nested actions.
I guess this is something for the "template context"!?
Another brainstorming idea is to support more "content areas" than
only 'sf_content'.
Maybe you could add something like setContent('sf_content', $content),
addContent('sf_content', $content) so one could easily use it as basis
for things like a wonderful page controller ;-) For example:
addContent('sidebar', $outputOfComponentX)
Regards,
Matthias
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" 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/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
