[TYPO3-dev] Moving the topic of the discussion a little bit -- Based of thread "Change roadmap..."

[Michael Scharkow]

JoH wrote:

> This is something I really would appreciate, since this would end the
> discussions and bring us a bit closer to a solution.
> You want smarty? - No problem. Use the templating API for your personal
> smarty extension.
> You want a Frontpage importer? - No problem too ... besides the problem that
> FP sucks ;-)
>
> The only thing I want to avoid is, that developers and admins will be forced
> to use a new so called "templating standard", be it smarty, XML or what
> else.

I fully agree with you here. I think we should offer pluggable 
templating options (so only add a template class register), so everyone 
can choose to their liking.

Actually, I thought the whole topic was about changing the *core and 
system extensions*, so that we get rid of hardcoded in-place HTML in the 
TYPO3 code. Only for this, I'd rather have *one* standard in using 
templates, and for the reasons I mentioned in the above post, I'd favour 
PHP because it seems like an obvious choice.

> After all TYPO3 is a framework. So it should be possible to plugin a
> different module and completely change the way of templating with a single
> klick.

Yes, it should be. And it's not too difficult to implement, really.

Greetings,
Michael