<[EMAIL PROTECTED]> wrote:
While I agree that there needs to be a good way to use any template engine, I know switching is the wrong thing to do right now. There is way too much invested. I think Kevin is an the right track in how he is dealing with this issue.
It is quite possible that the end templating system maybe something completely different or some wierd marriage between Kid and Cheetah. It might be wise to create a KidVsCheetah? wiki page in trac that has all of the complaints. Once all this information is in one place we can effectively make decisions.
Now, I will just add this (here only):
If this is to work, in my opinion, (and by "work" I mean be successful
enough to challenge Rails), then Cheetah must be enabled as an equal
templating language to Kid (at least). Kevin, you don't know me, but I
dare make this post for the good of Python. Kid may be technically
superior in every way to Cheetah (I don't know), but is the least
popular choice you made for TurboGears. Cheetah is a lot more popular.
You obviously love Kid; I suspect you think it is the best choice you
made in creating TurboGears.
While I agree that there needs to be a good way to use any template engine, I know switching is the wrong thing to do right now. There is way too much invested. I think Kevin is an the right track in how he is dealing with this issue.
It is quite possible that the end templating system maybe something completely different or some wierd marriage between Kid and Cheetah. It might be wise to create a KidVsCheetah? wiki page in trac that has all of the complaints. Once all this information is in one place we can effectively make decisions.
But if you give in on this, you will be amply rewarded, but on the
other hand, I do not believe a Kid-centric TurboGears will compete
effectively with Rails, for it will signal continuing division and in
Python land.
What will happen when the next great template language comes along? Or when TG tries to merge with another framework that has yet another template language?
-- David
