On 12/22/05, _max <[EMAIL PROTECTED]> wrote: > > > 1) lack of chosing template language (which is kind of religion) > > Yes, maybe TurboGears should do it RoRs way here: no default (real) > template language. > > It's too late to switch templating languages, but maybe its possible to > make widgets and other template sensitive parts of TG "template > independant" like RoR, wich is not the same thing as supporting Kid & > Cheetah everywhere, less hassle, and that would please everyone (i > think).
The danger of this is that if we stop making assumptions about a template language to use, we miss out on some features that we get by making the assumption. (Examples: i18n has a Kid filter that makes it easier to provide the correct text, and the widgets allow you to use the same templates you use for the main code... which is a bonus.) One good thing I'll say about this thread: most people are asking for Cheetah specifically. In some ways, that's better than having a bunch of messages where people say "yeah! and I want Myghty" and others say "I want PSP". And let's throw in XSLT for Sylvain while we're at it :) There are actually interesting ways that changes on the parser end could make Kid more attractive to the people who like Cheetah without making it less attractive to the people who like Kid. David Stanek mentioned to me the idea of using a more liberal HTML parser (which would take somewhat cruddy HTML input and produce nice HTML output on the other end). Anything that can ultimately end up as Elements (and then serialized to plain text or HTML or XML or whatever) is fair game to be mixed and matched with the rest of Kid output. That's one nice thing about Kid's architecture: if you hand it an Element to render, it just drops it into the tree, ready for serialization. I do think some people dismiss Kid a little too readily. And py:match is addictive when you use it (and, as far as I know, Cheetah has nothing like it). Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
