[Typo3-dev] Smart Content Rendering

[dan frost]

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.

We can define a DTD to ensure the structure / 
syntax and let the underlying stuff 
(tslib_content.. blar blar blar) concentrate on 
processing.

But - this should be part of a much large strategy...

dan


> I hate and love typoscript at the same time, the biggest problems with 
> typoscript are
> 
> 1) Error reporting, you can't see a error when you try to do something 
> that's not possible.
> 2) In compleetnees, things are possbile in some areas of typoscript 
> while not possible in others...
> 3) Slighly different syntac on different areas...
> 
> If you can solve the above tree then I think you have a wonderfullt 
> configuration language.
> obts is IMHO the way to go so we can stay with good-old-typoscript for 
> backward compatibility,
> and going for obts (IF it solve the above items) in feature..
> 
> without TS I couldn't 'glue' my site together.
> 
> Ries