Opinion: Template Engine Integration RIP?

ciadmin, A "standard" CI library built in sounds great. As it will be the defaco. This way any "additional" engines will need to follow guidelines to be used (just like today).
I just didn't want to see somebody expect parser "foobar" to be the defaco and then everything not using that breaks. Like in there instructions "just add this to make foobar your default parser and your views will work". Instead it could be (just a example of course) "just add ".lex" => 'pyrocms/lex' to your view render config file and your views will work"

Just a FYI https://github.com/zordius/lightncandy is the handlebars library I currently use and as ivantcholakov said one of the main reasons I chose it was because the client and server side "views" can use the same syntax. Which in turn is one less thing for our designers to learn.

DMyers

https://github.com/ProjectOrangeBox / https://github.com/dmyers2004