On 12/21/05, Sylvain Hellegouarch <[EMAIL PROTECTED]> wrote: > Kevin Dangoor wrote: > > Keep in mind, though, that you'll likely miss out on the other cool > > stuff like widgets i18n.
That's the tradeoff. Use Kid or port these extra features yourself. Or maybe a third-party maintainer will arise to do it for everybody. > The ultimate experience would to be able to switch any layer of TG to replace > by > another that respects the same API :) > > What I'm dreaming? That may be unfeasable in this case. But if you can think of a way to do it, it's certainly worth making a proposal. The interface between all these "extras" and Kid seems to be an ElementTree node. The extra thingy generates it, and Kid knows how to interpret it. So maybe if Cheetah knew how to interpret it too, everything would be hunky-dory. (My, I'm using a lot of corny slang today. It must mean I'm very tired.) Actually, if the thingy has a suitable .__str__() method that produces the appropriate HTML, the work would already be done. Oh, but ElementTree produces XML not HTML, darn. A Cheetah filter would have to do the conversion. Well, that's not an insurmountable task. -- Mike Orr <[EMAIL PROTECTED]> ([EMAIL PROTECTED] address is semi-reliable)
