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

[JoH]

>  >>Check out Smarty, seriously.
>  >
>  > I will ask our designer to learn programming. He will be very
>  > happy....... Hope, he will not leave us...
>
> If your designer does the HTML Templates he is programming already.

Wrong. If my Designer does the HTML Templates, in most cases he will be
using Dreamweaver or something similar and has got absolutely no idea about
programming, smarty or HTML at all.

> And doing proper HTML & CSS is a lot more difficult then learning
> basic smarty syntax like {$mytext|upper}.

Of course, but most of the Designers are not doing proper HTML & CSS,
because they simply don't know, what is regarded as proper and what not.
They are the same people that will be importing a whole page into one single
RTE out of a powerpoint document they created for a presentation.

> Your designer will _LOVE_ this freedom he gains, e.g. alternating
> layouts with loops and so on.

My Designers are using a mouse (1 button only of course...) and they really
don't like loops and knots in its cable ;-)

> If he is just a designer, you will need someone coding the templates
> anyway.

Maybe - but this will be doing the TypoScript Setup anyway, so why should I
bother him with another coding syntax he would have to learn?

> And for the Smarty/PHP templateing comparison: The good thig about
> Smarty is it wonderful chaching mechanism, where it compiles the
> templates into pure php -> so it is as fast as PHP, once cached.
>
> I would love to see Smarty integrated in TYPO3 - if not, I would still
> like to have freedom of choice which template engine to use - means:
> It would be nice to have a modular templating API which is able to
> serve templates with different enignes.

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.
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.

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your knob sometimes!)
Dieter Nuhr, German comedian
openBC: http://www.cybercraft.de