[Typo3-dev] Smart Content Rendering

[Martin Kutschker]

dan frost schrieb:
> ObTS has the architecture to support these.
> 
> I think we need to define exactly what TS is for - and not use it for 
> anything else.
> 
> I really like the idea of defining the structure in XML, but allowing TS 
> syntax as well. This would allow use to write in TS, parse it into XML 
> (DOM, PHP5) and the core (tslib_content, obts etc) would use XML objects.

My favourite idea is to use XML only for describing the TS syntax and 
grammar, but using TS for the actual configuration.

With the declarative XML you can verify the TS syntax, you can build a 
TS wizard with all kinds of bells and whistles. Extensions could even 
provide their own TS objects by providing the declarative XML and the 
necessary PHP code.

To make this really useful I'd a) streamline the current TS 1.0 to make 
a TS 2.0 even if it's not 100% compatible and b) revamp the PHP code to 
something like obTS (each TS object will be a real PHP object).

Perhaps we could gain a boost in performance if the new TS 2.0 could be 
parsed by a TYPO3 PHP extension.

But any changes from the current TS to whatever may only be achieved for 
TYPO3 5.0. It might be possible to create the new system parallel to 4.0 
and 4.5 and integrate the new system to the 5.0 codebase.

Masi