[TYPO3-ect] Improvement of the template engine

[Kai Laborenz]

Ernesto Baschny [cron IT] schrieb:

>>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.
> 
> 
> This is how it is already. There are already extensions rendering stuff
> in HTML-templates, and others rendering with pure TS, and I'm sure there
> are others that might even depend on smarty. This currently depends on
> the extension developers taste.

Right. Thats why we discuss to find a better way, I think..?


>>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.
> 
> 
> I don't think we will be able to do that, and I don't even think we need
> to do that.

Why?


>>Maybe another approach is to do all the templating in the core (or
>>somewhere 'near' the core).
> 
> I might be repeating myself: but this is already available and being
> used. Its called TypoScript and its content objects.
> 
>>Extensions just request certain functional structures (like a table) and
>> get the template markup for this structure delivered.
> 
> See CTABLE cObject for rendering data as a "table".

Maybe the table was not the best example to make my point because a 
table is a functional structure and a markup element as well. I expect 
the extension also to reques something like a "calendar single view" or 
something. This is basically the idea of microformats 
(www.microformats.org) - to define certain html markup for functional 
elements.

Greetings, Kai