In my opinion, trying to resume this whole discussion: 1- Some people said that if Twig is introduced as default, it will impact plugin development. Well, since Symfony2 isn't still final, it's the best stage where this engine can be introduced as default; 2- Some people also said that Twig increases the overall Symfony learning curve; I've been a Django developer for some time, and the easiest part of Django to learn, by far, was its templating engine. Considering that Twig is hugely inspired by this engine, I very hardly believe that developers/designers/whatever using Twig will also learn it quickly.
That said, +1 for Twig as default. It's loosely coupled. It rocks. :-) Cheers, Diogo P.S.: Symfony itself also rocks. Thanks for giving the PHP community such a great framework, guys! :-) On 22 set, 09:36, Fabian Spillner <fabian.spill...@gmail.com> wrote: > For my opinion: > > Twig can be default, if it can be disabled and ... > > It should be possible to have mixture of Twig and PHP templates on the > bundles. > > For example: The backend team wants to create quickly the PHP > templates to test the model outputs > and send the work to frontend team to migrate it into Twig templates. > > For me Twig as default template is important point: > > The developer is forced to make the templates clean and simple for the > web designer. > He must learn to put the logic into the controller / model and not > into the templates. -- 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
