I didnt mean complex by that, but all the xsl like features (match mostly, the validation of the template) are imho not that imporant to a template language when it deals with python behind (I don't generate onyl xhtml/xml/html documents with my templates, i'd like to be able to generate mail/csv/latex without too much workarounds).
"XSL is only performant because of work put in on the individual implementations to make it so." Yes just like Cheetah, there s been a huge amout of work put into this project , it s a bit sad not to do take advantage of this. If i was about to bring the best-of-breed i d use Cheetah or XSL (but Cheetah is more friendly to newcomers in a python based framework) , but then again it s a matter of personal taste. I began to use cheetah a few days ago so i am not 100% confident with it yet but i liked it so far (i am no kid expert either, but i ve played with most of its functionalities). "TurboGears will not stand in the way of people using Cheetah, and can go so far as allowing Cheetah templates to receive data via turbogears.expose. " Yes, looking foward to use some of the great features from the Toolbox, i guess i am just sad having to give up on widgets & i18n for now. "But, going beyond that will just make things messy" Yes certainly, i didn't think of all the implications for sure (haven't tried widgets yet, maybe kid got improvements in terms of performance lately too). Sorry for the spelling mistakes, it not my native language.
