Twig as our template engine

[EXreaction]

The old one was removed, everything is now rendered with Twig.

[Mess]

I'm very exited to see where this will take us, and how phpBB's designers will embrace this.

[Kamahl19]

Great, thats better. So now we can use all features of Twig including blocks, filters etc using Twig syntax, and some of the features using old syntax, right?

[EXreaction]

Almost all Twig functionality works using our syntax. A few things, such as: {'a string'|upper} don't work, but at least all Twig tags and filters on regular variables should.

[Kamahl19]

But Twig syntax is available too, right? Will there be some list in wiki, listing all features in both syntaxes?

[EXreaction]

Technically, yes, but whether or not we want to allow the use of the Twig syntax is another question. That question will be addressed in another RFC before 3.1.0 is released, but we'll wait on asking that until Twig is actually merged into 3.1.

[Danielx64]

Q: the thread that explain how to turn a mod into a ext is now useless? (nv news page example)

[Kamahl19]

No, I dont think so unless you dont want to use new features from Twig... All old syntax should work.

[EXreaction]

Where is that thread?

Everything functions about the same for extensions, except there were some bugs fixed and previously incorrect behavior corrected.

[MattF]

Q: the thread that explain how to turn a mod into a ext is now useless? (nv news page example)

No, it is still totally applicable.
https://github.com/nickvergessen/howto- ... phpbb31ext

The new TWIG engine is a transparent change... All template syntax is unchanged, so far as we are concerned. Except that if you know TWIG, you can actually use that in your template files as well as the standard phpbb syntax, if you wish.

What I want to know is, does the new TWIG engine (by the way the amount of work you did on this Nathan is awesome) address the biggest limitation of the template system for extension developers: the inability to in-line edit lines of code in template files?