On 9/22/2010 9:09 AM, Fabien Potencier wrote:
Hi Jordi,
...[snip]...
- On the downside, I guess Twig has a bit of a learning curve, but then
again people must learn the symfony "keywords" anyways, like
$view['router'], that aren't especially obvious to a non-sf developer.
So it's not like PHP templates are completely straightforward, and Twig
syntax is quite simple and well documented.
I think this is quite the opposite. Sure, for a developer, Twig is
something new. But for web designers, I think they can learn Twig must
faster than PHP (HTML designers at Sensio now use Twig instead of PHP
and they love it).
Fabien
Thoughts?
Cheers
As someone who's 'new' to sf in general, and sf2 in particular (having
only done some light tinkering around with it all on an Ubuntu VM on my
rusty old Windows laptop), I'd like to put in my vote for going with
Twig - it sounds fantastic to me (and I come from more of a designer-y
background).
For me looking/thinking of moving a large-ish old-style php app (read
messy) to sf2, the thought of having to learn a little bit extra to gain
in the templating department is no biggie -- learning the rest of sf2 is
going to be the real hurdle to cross...
So my vote would be to remove the templating engine options and just go
with a lean, mean Twig.
Cheers,
-Chris
--
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
