On 22.09.2010 12:51, Stefan Koopmanschap wrote: > But again, the option to switch to plain PHP (or another template > engine, for those that want/need another template engine) should still > exist for the more advanced users.
A decent option maybe for maximized performance, would be to have a Twig-only view layer replacing the current Templating component, and then keep the Templating component in the sources so it can be just enabled via config value, and that one would still default to php templates or allow any renderer to be used.. But that could mean you would lose the ability to use most of the Bundles that come with templates. It's clear looking at the past that the default engine is what will drive 99% of the opensource code, shared plugins etc. So it becomes very difficult to avoid it, much like it's tricky to use non-PHP templates in sf1 (afaik). Cheers -- Jordi Boggiano @seldaek :: http://seld.be/ -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
