[TYPO3-ect] Reboot: Templating

[Jan-Hendrik Heuing [DD]]

Hi!

Just wanted to get the template discussion going again. I do not want to ask 
you for which templating mechanism you like most, it's more about those 
details.

I would like to get some feedback on a few things for either:
- TV
- TS-TEMPLATE-Object used in your page template
- using the same, those subparts and marks in your PHP
- Smarty
- Whatever you use

Feedback on those things would be great, and if you have other important 
things to mention, I am also interested:

- Workflow: How is your workflow, is it working well, or what are the daily 
problems you find annyoing? (TV: I don't like the way TS is connected in 
those XML files; TEMPLATE subparts/marks, there is no logic at all in those 
HTML-templates, you have to wrap-wrap things, etc...)

- "Interfaces": I am not talking about APIs, but rather interfaces to users. 
We are sometimes having the case, that people doing html-templating, but not 
the backend integration. Would be interesting, what usergroups take part of 
the workflow, and in which specific part. (TV: Difficult as last time I 
looked at it, the xml-files had to be rewritten, but I guess one could work 
that out; TEMPLATE: Here you have a plain html-file with some "syntax" in 
terms of subparts and marks, which HTML-users get used to.)

- Functionality: What functionality would you like for templating? Some 
logic would be good I guess, but more than that? Parsing of fields? 
(Possible with xslt if you pass through to php in the php5-implementation, 
interesting)


I would like to sort of find a way, which could work out as a base for 
further thoughts. It would be great to see if we need some template engine 
wrapper, as we stick to various template engines, or if we finaly find one 
or 2 which work out in most cases. I am in favour of some xslt-method, which 
can be used by html-template-builders as well; TV is famous these days, the 
old TEMPLATE-object us used a lot, while I am not quite sure if it does have 
any powerful features itself beside it's full integration, so that people 
would use it in the future anyway, if alternatives are available.

Would be great if you take a moment to give a short review of your daily 
templating-story.

thanks, JH