F Wolff(e)k dio: > On Ma, 2008-11-03 at 10:12 -0700, Wil Clouser wrote: >> I haven't used Django so I can't say for sure, but my guess is I'd >> rather use django's templating. Kid is frustrating to use. For >> example, having to pass in every string you use to the view and then >> if you use a view function you have to pass it to that as well. Why >> can't Kid just access the _() function itself and save us all the work >> of passing those strings around as well as all the extra code we have >> to write? >> >> Anyway, it's a nice idea, but I'd rather get away from Kid as well. >> >> Wil > > I think the big value of this is that it means we don't need to touch > the templates for things to get working on Django, which just means one > less thing to worry about, and one less source of bugs. After it is > working, I guess we can change again. > > Personally I like kid, but I don't have a lot of experience with > comparable software. > > Friedel
This is useful for the migration part, so we can focus on other parts of the code. But once the migration is complete, I think we should drop Kid, apart from the reasons Wil has already commented, it seems Kid is one of the slowest Python template engines out there[1][2] so this is an important handicap. Julen. [1] http://www.makotemplates.org/ see Features section. [2]http://genshi.edgewall.org/wiki/GenshiPerformance ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
