>> > Apparently, the internationalization needs kid to work in JS file. >> > Didn't really dig too deep as to why exactly. I easy_installed >> > TurboKid and everything works fine now. >> >> > Not sure having to install kid is the best solution though, can this >> > be fixed any other way ? >> >> TG 1.1 still uses Kid for the TG widgets including the JSLink. This is a >> small inconsequence in TG 1.1 we need to live with until TG 1.5 will be >> released, where Genshi is the default engine not only for page templates >> but also for the TG widgets. But maybe we should improve the warning >> message by adding a hint about installing TurboKid.
Now that we are at genshi and kid, what do you all think about *not* switching to genshi as the default template engine since the argument used to be that kid is abandonware while genshi isn't but this is no longer the case. Both are pretty good and both are abandoned, so why should all that work go into switching out kid for genshi in tg1? Are there specific arguments against kid in favor of genshi that are not related to kid being not maintained anymore while genshi is (was)? Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
