On 12/22/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > sorry, clicked "enter" unintenionaly: > > IMO there are two disatvanatages in TG: > 1) lack of chosing template language (which is kind of religion) > 2) lack of url-name mapper > > I heard second will be fixed using routes.
Probably so. I'm interested in hearing your use case for #2... CherryPy is pretty flexible when it comes to URLs. (Compatibility with existing URLs is a use case that I do agree a mapper will help out with). > Fixing first issue would be big step towards users - eg. I have big > template library in cheetah and dont want to rewrite them. Yep. I agree that this is a valid use case for providing the ability to plugin a different template language. > > Maybe additional value for decorator (tmpl_language = "KID") would do? > > I think i could code decorator to use cheetah template, but heard that > tg uses incremental sending - kid sends rendered part of template, > what couldnt be done in cheetah. I've already seen a decorator for using Cheetah. It's not hard, because you can just return a string and CherryPy will send it along. A plugin would be more graceful. Kevin
