On 12/20/05, _max <[EMAIL PROTECTED]> wrote: > Kid feels bloated, lots of features which are imho useless and/or costs > too much in terms of performance , most of the time i end up hacking > around kid to avoid its issues. I am one of those who think a template > language has to stay simple (i think it s also django approach).
I'd be interested in examples here. I don't find Kid to be a particularly complex template system. > I like the idea behind Kid (xsl/python mix) but not at such a > performance cost, i'd rather have controllers serializing return > dict(...) in XML and using XSL. Performance issues can be dealt with (and David Stanek has looked at this some). XSL is only performant because of work put in on the individual implementations to make it so. Likewise, Kid is a good language to work with and there are many ways to address performance issues in Python. > Cheetah feels like an improvement for a lot of people, i am sure it > would bring some new ppl to TG . It s rock solid/stable, has some > really nice features Kid lacks (powerefull caching, oo, no hassle with > well-formedness/entities, document output format). "no hassle with well-formedness"? Ick. Especially as the migration gradually occurs to XHTML, having well-formed documents and a system that supports that will be a big bonus. I'm not sure what you mean by "document output format"? I'm also not certain that it's the template tool's job to do caching. There are many places were one can conceivably do caching. > Not to mention all the cheetah+framework "X" web apps which could be > converted to TG faster. This is actually a real use case that I can get behind. In "What TurboGears Is Not" [1], I state that having two ways of doing something is fine as long as people know very clearly when to use one or the other. Making it possible to easily send data to a Cheetah template as a temporary compatibility measure while migrating to the whole framework is fine. But trying to fully integrate another template language (i18n, Toolbox, widgets, etc.) is not in the cards. 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. But, going beyond that will just make things messy. [1] http://www.blueskyonmars.com/2005/12/20/what-is-turbogears-not/
