On 12/20/05, _max <[EMAIL PROTECTED]> wrote: > > 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).
I think that match is one of Kid's coolest features (and the overhead of match is surprisingly less than you'd expect). The great thing about match is that it allows you to create templates that are fully viewable in a browser on their own *and* have app-wide styling applied to them at runtime. Kid provides a great collection of ways to structure your templates so that it makes sense for your application style. Current versions of Kid can produce plain text output. Admittedly, Kid is not as good at plain text as Cheetah, but Kid works great for HTML/XML which is a large portion of a webapp's output. Rather than optimizing for the less common case, I thought it best to optimize for the most common case. > "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. True, this is a matter of taste. I would say that Cheetah *is* the best-of-breed template language for things other than XML/HTML. > 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). I've used Cheetah quite a bit, and I should be clear that I'm not trying to sound negative about Cheetah. Cheetah is good at what it does. I just think that Kid is better at doing an important and common webapp task (generating HTML output). > "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). I honestly don't know if Kid has had performance improvements applied, I just know that some looking into it was going on. I do believe that any performance problems can be addressed through the many means possible in Python. > Sorry for the spelling mistakes, it not my native language. Your message seemed quite clear to me! Thanks for taking the time! I know it is more difficult to write in another language. Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
