Hi,
so you say the template has to prevent the developer to access classes they
should not access in the template?
That approach failed with JSP taglibs, and led to the templates we today
know.
I also cannot see why we say "do what you want".
I would say: Use the static helper methods.
If we end up with the sfHelpers->get('url'); thingy, fine then we recommend
that.
But I asked the question what benefits this brings and what use case
supports that.
.: Fabian
On Mon, Jul 7, 2008 at 9:47 AM, Dennis Benkert <[EMAIL PROTECTED]>
wrote:
>
> > I do not like the idea of "go on and use everything you want in your
> > templates and good luck with finding the right way".
>
> I agree with that. The framework has to leas you the right way by it's
> own code. In my opinion giving the developer to much room for bad
> things leads to same problems php suffered for years.
>
> - Dennis
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
