[TYPO3-team-core-v5] Templating Engine

[Sebastian Gebhard]

Sebastian Kurfürst schrieb:
> It's no final decision yet, but we are seriously thinking about 
> including the templating engine in TYPO3 4.4 as well - so people can get 
> used to it, before they migrate. Besides, I think there will be people 
> writing Smarty or PHPTal connectors for v5 - so you'd be free to use 
> these as well.
> Does this sound reasonable to you? :-)

I like it to have the choice which rendering engine I take, but imho it 
would be better to provide a fixed amount of them like:
- Traditional TYPO3 Template Rendering with markers
- Smarty
- PHP rendering
- beer
I think this is a range of syntaxes of which one can get used to. But if 
every second package developer implements it's own rendering engine with 
maybe some odd syntax, security issues, bugs or lame performance I think 
one of your aims to raise code quality will miss.
Why do you want to be so flexible? Developers are exactly taught how to 
write PHP-Code to fit it to FLOW3 to ensure quality, consistency and 
good understanding, why can't this get along with the rendering engines?

> I've been thinking about it, and I think it could work with the current 
> concept as well.
> However, I think that the above syntax is too verbose for my taste - It 
> is 8 lines, just to print a single link with some parameters? My gut 
> feeling is that this would be worse than it is now...
> Why do you feel the above syntax is better than the one described by me? 
> I'm interested to hear your opinion :-)

I get the point. 8 lines might be way too much for one link. But 
designing this I had the XML-Syntax of nowadays' flexforms in mind, 
which also often uses a lot of lines for one single field. The advantage 
is the flexibility, because for you as a core devloper it might be 
easier to implement new options and for the integrator a link with a lot 
of parameters is easier to overview.

> Beer3 means: Best Ever templateEngine Replacement - but it is no serious 
> name :-)

Ok, I'll keep that in mind. Maybe I can come up with some good suggestions.

Great work so far!