Bumping this again... Between the lines of my last post in this list<http://groups.google.com/group/symfony-devs/browse_thread/thread/2fe8f9709ed9458c>is the idea that there could be a widget to include a partial and another to include a component.
We could use these widgets in the partial helpers, in the action, in the forms, and in the new admin generator... Isn't it the best solution? François 2008/9/26 Francois Zaninotto <[EMAIL PROTECTED]>: > I thought about something closer to a service locator (until we have a > service container and IoD in symfony 2.0) available in several > objects, including the action... But maybe I'm reinventing the context > object. > > If nobody has a better solution, a proxy method in the context object > will do the trick, I suppose. > > François > > 2008/9/26 Joaquin Bravo <[EMAIL PROTECTED]>: >> >> What about a new function found only on the actions that loads a >> partial or a component? >> >> Inside an action: >> >> $this->loadPartial(); >> $this->loadComponent(); >> >> On Sep 25, 9:41 pm, "Tom Boutell" <[EMAIL PROTECTED]> wrote: >>> On Thu, Sep 25, 2008 at 6:38 PM, Jamie Learmonth >>> >>> <[EMAIL PROTECTED]> wrote: >>> > Well, I know that many feel the helpers should in fact be classes with, for >>> > example, a whole bunch of static methods in which case they could just be >>> > autoloaded. >>> >>> Yes, I'm inclined to agree with that. It's a little wordier but so >>> many problems go away. >>> >>> -- >>> Tom Boutell >>> >>> www.punkave.comwww.boutell.com >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
