But this is a different issue Pablo. This is about documentation, not about technical choices. I am sure the documentation will list all options (as the current document is awesome enough as well). And yes, one might see a blogpost by me about how to use plain PHP as I prefer that for my own projects, but I definitely think that for projects that involve more than just my input, especially when also working with designers, Twig is a much better option.
On Wed, Sep 22, 2010 at 3:46 PM, Pablo Godel <pablo.go...@gmail.com> wrote: > Stefan brings a good point. I always disliked projects that used smarty for > example, I did not want to use something like smarty in any project I was > involved. I did not see any advantages and there was that extra overhead. > Now, this was in the past, before Twig existed. Twig does bring a bunch of > additional features and does not suffer from the performance hit, but the > notion that there is a templating engine, an extra syntax etc, can turn some > developers away. It has to be well documented that PHP can be used, but more > importantly it has to be highlighted the advantages of using Twig over PHP > as most have been described in this thread so it will help those "ignorant" > developers like I was/am :) > Pablo > > On Wed, Sep 22, 2010 at 6:51 AM, Stefan Koopmanschap > <stefan.koopmansc...@symfony-project.com> wrote: >> >> I think that Twig should be bundled and be the default, but that plain >> PHP templates should still be an option. >> >> I have a personal distaste for template engines and while Twig fixes >> most of the problems I have with template engines (like performance), >> I still dislike the syntax. However, in most projects, the syntax is >> not my problem since there will be other people (designers, frontend >> engineers) that handle the templates. >> >> However, for other projects where I am responsible for the frontend >> (like my own private projects) I would like to have the option to >> switch to plain PHP, which I like much more. >> >> As Jordi mentioned, defaulting to Twig will ensure that >> lesser-experienced developers will not be able (or at least have a >> much harder time) to "break" the MVC concepts. And I think this alone >> would be a good reason to switch to Twig as the default. >> >> 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. >> >> Stefan >> >> On Wed, Sep 22, 2010 at 10:11 AM, Keri Henare >> <keri.mailingli...@henare.co.nz> wrote: >> > I think that Twig should be bundled but not default. PHP should stay the >> > default for templates. >> > >> > Kind regards, >> > Keri Henare >> > --------------------------------------------------- >> > Chief Technical Officer >> > Pixel Fusion >> > >> > [e] k...@pixelfusion.co.nz >> > [w] pixelfusion.co.nz >> > [m] (+64) 021 874 552 >> > [p] (+64) 09 550 3084 >> > >> > Zend Certified Engineer - >> > http://www.zend.com/en/yellow-pages#show-ClientCandidateID=ZEND013450 >> > >> > PLEASE NOTE: I check my email 3 times per day and will respond at these >> > intervals. For anything urgent please ring me. >> > --------------------------------------------------- >> > >> > On 22/09/2010, at 8:07 PM, Lukas Kahwe Smith wrote: >> > >> >> >> >> On 22.09.2010, at 09:39, Jordi Boggiano wrote: >> >> >> >>> And for PHP developers, as I already said learning Twig is really not >> >>> much work imo, took me about 10minutes to get everything up and >> >>> running >> >>> when I switched my Sf2 project to Twig. >> >> >> >> just in case people arent aware, there is already quite a bit of >> >> documentation for twig: >> >> http://www.twig-project.org/ >> >> >> >> please spend 10 minutes to look at the site before making a decision >> >> pro or con .. >> >> >> >> 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 >> > >> > -- >> > 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 >> > >> >> >> >> -- >> Stefan Koopmanschap >> Symfony Community Manager >> stefan.koopmansc...@symfony-project.com >> >> -- >> 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 > > -- > 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 > -- Stefan Koopmanschap Symfony Community Manager stefan.koopmansc...@symfony-project.com -- 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
