2014-10-09, 09:17 PM
Quote:Twig will be the template engine.
Out of curiosity, what made the team choose Twig and how does it compare to other template engines in terms of functionality, syntax, etc. ?
2014-10-09, 09:17 PM
2014-10-09, 09:27 PM
Will, first of all, you forgot to quote the 2nd part:
Quote:(Not sure if this will be effected by the framework change or not)
2014-10-09, 09:30 PM
That information is outdated. It looks like Blade will be used now.
Personally, I prefer Twig. It has a simple code style that allows the use of many useful expressions, but can also be easily locked down and secured (eg: stop the running of arbitrary PHP functions... Unlike Blade). It's also very easily extensible to add new filters and more. A lot of editors also have syntax highlife get and support for Twig.
Personally, I prefer Twig. It has a simple code style that allows the use of many useful expressions, but can also be easily locked down and secured (eg: stop the running of arbitrary PHP functions... Unlike Blade). It's also very easily extensible to add new filters and more. A lot of editors also have syntax highlife get and support for Twig.
2014-10-13, 06:06 PM
(2014-10-09, 09:30 PM)Euan T Wrote: [ -> ]That information is outdated. It looks like Blade will be used now.
Personally, I prefer Twig. It has a simple code style that allows the use of many useful expressions, but can also be easily locked down and secured (eg: stop the running of arbitrary PHP functions... Unlike Blade). It's also very easily extensible to add new filters and more. A lot of editors also have syntax highlife get and support for Twig.
What's the benefits of using Blade over Twig then?
2014-10-13, 07:06 PM
It's built into Laravel. It's not decided, but most of the rest of the team seem to prefer Blade to Twig.