On 10/7/10 3:59 PM, Miha Vrhovnik wrote:
As Fabien didn't post his final decision yet I think that he didn't yet make it.
The change I made was only a technical change so that is no "default" template engine anymore. They all feel like first-class citizens.
So, the problem now is what do we do in the documentation. Fabien
I'm voting +1 for twig. For one I've newer liked the php in templates as I find them unreadable and hard to follow. Secondly None of html/css design guys I've been working with didn't like/wouldn't learn php so. Also from all the companies I've worked for all except one were using some sort of templates. IF I remember them correctly it would be in the following order: php, custom made, flexy, symfony, smarty, dwoo. And this was depending on the project so in some companies we've used more than one. Someone above mentioned that there is a learning curve, yes there is for each engine, but I find it quite small especially with good docs. Regards, Miha
-- 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
