[TYPO3-ect] Improvement of the template engine

[Kai Laborenz]

Ernesto Baschny [cron IT] schrieb:
> Kai Laborenz schrieb am 26.01.2006 22:01:
> 
>>Ernesto Baschny [cron IT] schrieb:

> I think you missed the point where I said that this works as well for
> HTML-templates but isn't bound to HTML-templates! It doesn't add
> complexity, it adds flexibility.

I undestood you right. More flexibility often means more complexity. 
Thats not always bad - the question is: what do I get and what do I have 
to pay...

The advantage of the open approach is that everybody can use his 
favourite templating mechanism.

The drawback is you have some extensions with html templates, some with 
smarty, some with TypoScript and some with some methods yet unknown.
You get a variety of solutions for one problem. More complexity.

We don't need three or four ways of templating. We need one way - it 
just to make a decision wich way is the TYPO3 way.

Maybe another approach is to do all the templating in the core (or 
somewhere 'near' the core).
Extensions just request certain functional structures (like a table) and 
  get the template markup for this structure delivered.

Gretings, Kai