From: deelan <de...@in...> - 2003-07-26 13:29:56
|
Huy Do wrote: > Hi All, > > I was just after some opinions on the suitability/necessity of using > cheetah for templating together with a HTML DOM library. > > If my templates do not have any markup whatsover i.e just using the DOM > library to generate/create the HTML tags, I can't see the advantages > cheetah would offer over a normal python class. This is my > understanding, but I if anyone can provide some more/other insight, it > would be greatly appreciated. i think the choice it's a matter of personal taste and your team "modus operandi", for example i'm rewriting my blog, draft & experimental design is: http://www.deelan.com/redesign/03/ i've built it using dreamweaver, so it makes more sense to me *not* to covert it in DOM calls. i don't feel very confortable in writing html code in the webware servlet either (writeHeader(), writeFooter(), etc.), you split and mess things up. cheetah comes handy if you have to pass some markup intensive pages to the "HTML guys" in your team... obviously they are used to work in htmlkit/dreamweaver/whatever and they understand only HTML, in this case cheetah it's pretty understandable to them too. i can't say the same for pure python DOM calls. oh, by the way you can mix the two techniques together. there's a good intro about the template-approach here: http://jakarta.apache.org/velocity/user-guide.html cheetah is pretty close to velocity on some aspects, hence some key ideas still apply. later, deelan |