Mike Orr napisal(a): > But I'm not too happy about Kid. Yes, my *output tags* have to be > valid HTML, but why should my control structures be > (#for/#if/#def/#extends). The significant word (py:for) is buried in > a tag attribute where it's easy to miss. I'll have to put comments > around every for-block and if-block to make them stand out. And Kid > doesn't have if/else!
Exactly. People with a strong PHP background absolutely love Cheetah for being Smarty, but much, much better. Kid, on the other hand, strikes me as software-that-knows-better -- and I say, don't worry about me producing invalid HTML, I sometimes want exactly that (on very rare occasions, but still.) All visibility arguments are also valid. (You'll probably think that I just don't like Kid; and you're right :)) I understand the strong push for having a single templating engine, but IMHO Kid is just not flexible enough. If I could do something like this at the beginning of the template file: # shebang, emacs and python inspired: -*- template: cheetah -*- <cheetah code here> I'd be more than happy.
