On 12/29/05, Mike Orr <[EMAIL PROTECTED]> wrote: > 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.)
Ideally, it would be easy to do simple substitutions and such for non-XML formats (CSS and JS) using Kid as well. > 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". Yeah, that smelled funny to me, too. The scheme identifier seems like a good way to go. Good thing this is alpha, so I'm allowed to make changes. (Plus, afaik, I'm the only one who's written a template plugin :) > > > 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. No kidding. > 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. This is a good point, and I think that having a page (or several) devoted to Python people coming in from other places would be a good thing. Kevin
