On 12/29/05, Ron Stephens <[EMAIL PROTECTED]> wrote: > > Hello Kevin > Jorge Vargas wrote: > > >For what I see people wanting Cheetah have this points: > > >1 - I need to output <format> and kid doesn't lets me > >2 - I just like it better > >3 - We should let people decide > > >for 1 and I think this is the most important part, why don't we made > >kid default for XML, XHTML and whatever it implements, and Chettah for > >everything else? > > I really like this idea.
Um, what non-HTML format is there that TG should support out of the box? (And I'm a Cheetah fan, sheesh.) And doesn't the new Cheetah-friendly template handler cover those cases? (I haven't tried it yet.) My main complaint about the template plugin is "wiki20.templates.main.tmpl" mixes module syntax with filename extensions in a schizophrenic way. Perhaps a scheme identifier at the front instead? "cheetah:wiki20.templates.main". > 3. This leads me to believe that not using Cheetah will be a major > reason why many people don't choose TurboGears. > 4. The better support for Cheetah you offer, the more people will > choose to use TurboGears. The more vocal you are about supporting > Cheetah, the better. If Cheetah support is offered grudgingly, this is > not much better than not suppoorting it at all. This turns on what "Cheetah support" means. Having full Cheetah integration is incompatible with other parts of TG depending on Kid's side features: mainly its ability to convert XML templates to an object model that can be transformed a la XSLT (py:match et al), and into which you can inject XML elements (e.g., widgets). One can imagine an abstract API that genericizes this for all template types, but it would be a heckuv a lot of work. Having minimal Cheetah integration so you can at least use a .tmpl file for output seems like a good start. This will pacify the large number of people who will not use TG without Cheetah. No, it's not about "market share". It's about using the best tool for the job, and if we think TG is the best framework for many jobs, we shouldn't arbitrarily hinder people from using it just because we're dogmatic about templating. Maybe they'll warm up to Kid gradually if it's not shoved down their throat at the beginning. Somehow, Cheetah support will have to be advertised with TG. Right now it's buried under "template plugins" on the docs page. http://www.turbogears.org/docs/ That could be: templat eplugins (Cheetah) template plugins (Cheetah, etc) Cheetah and other template plugins Also, TG is really marketing itself to two different audiences, and maybe that should be reflected in a second "About" page. 1) Some people just want an integrated solution, and don't want to hear about a second template system. The current About page handles this. 2) Experienced Python users often have specific ideas about what kinds of tools they prefer. So the second page would highlight TG's flexibility. This is where the tradeoffs of Cheetah could be discussed. -- Mike Orr <[EMAIL PROTECTED]> ([EMAIL PROTECTED] address is semi-reliable)
