On 25.09.2010, at 07:43, Fabien Potencier wrote: > On 9/24/10 11:56 PM, Richtermeister wrote: >> Hey Kris, >> >> without knowing anything about how SF2 and bundles etc work, but >> wouldn't it make sense - in the situation you describe - to allow each >> bundle to specify the template engine it uses? That way I can mix my >> php coded application with a twig bundle, etc. > > It will rapidly become a configuration hell. And frankly, it's not too much > work to add :php at the end of each template name. > > Here is another suggestion: what about removing the "default" templating > engine. What about making the templating engine part of the template name > mandatory. That way we are always explicit and there is no default per se > (technically -- of course, the documentation part is different): > > HelloBundle:Hello:index:php > HelloBundle:Hello:index:twig > > HelloBundle:Hello:index.xml:php > HelloBundle:Hello:index.xml:twig > > We can probably find a better naming convention. What about this: > > HelloBundle:Hello:index.php > HelloBundle:Hello:index.twig > > HelloBundle:Hello:index.xml.php > HelloBundle:Hello:index.xml.twig > > That way, when you are using the filesystem loader (and this is the case 99% > of the time), the last part is just the file name. > > What do you think?
then we just have to make sure that its easy to overwrite the name of the template in all bundles easily if someone wants to use a different template engine for a given bundle. regards, Lukas Kahwe Smith m...@pooteeweet.org -- 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
