[Typo3-dev] Smart Content Rendering

[Ries van Twisk]

Peter Niederlag wrote:

>Hi,
>
>JoH schrieb:
>[...]
>  
>
>>So lets improve it, like Dan already did with ObTS, instead of thinking
>>about ways to get rid of it.
>>    
>>
>
>Imho thats exactly the way to go. In my eyes Typoscript is much faster
>and flexible than any smarty or other technic.
>
>my 2 cents,
>Peter
>  
>
Aren't smarty and typoscript not two completely different things?
I have never seen smarty creating a menu for example,
not I have ever seen smarty making decissions based on external variables.
(I must admit, I use smarty but mostly for variable replacement and 
making simple decissions in my form).

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