On Tuesday 10 October 2006 18:22, Charl van Niekerk wrote: > Hi All, > > I really like the idea of migrating to django - I have researched the > platform some time back (I actually hoped we might be able to use it > for the translate.org.za website at some stadium since it looks very > nice) but never got around to actually playing with it.
Django is quite fun. The project has loads of documentation and the framework has very good support for most of the features a developer needs. I actually can't remember one thing I would need and it does not feature. Some have been complaining about it's ORM model, but that's going to be sorted out with SQLObject branch soon. But since Pootle already has it's own storage backend, that does not present a problem. > If we can throw kid out of the door that would also be really nice > IMHO because the installation of kid is somewhat complex since it has > dependencies and requires hacks [1] to get it to run sometimes. Yes, Kid templating will be replaced by Django's templates in near future, hopefully. > Anyway, I am interested though to know how this will impact Pootle > development. Since I need to learn Python I am thinking about adding a > password recovery feature some time (if nobody beats me to it) but if > we have to start on a "clean slate", would putting serious effort into > building the current main branch be worth the time or should one > rather focus on getting things migrated to django? What would the > focus thus be at this point in time, or am I running too far ahead? :) > > > Regards, > Charl > > [1] > http://translate.sourceforge.net/wiki/pootle/installation#installation_on_m >icrosoft_windows Frankly, I'm not sure. If you are already familiar with Pootle's code, then it's probably best not to wait. If you don't know Django yet, then maybe you could skim the tutorials first and then help migrating. I'm only afraid that during the migration, you might get confused if you don't know Django well yet. This is because I will try to make the migration as painless as possible, making sure not to leave repository in broken state. This will include mixing Django style with some Pootle's peculiarities. If it suits you, feel free to join. I'd be happy to help. :) Regards, Gasper ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
