Zejn Gasper wrote: > Hello, fellow Pootle users! > > I've started to port Pootle from jToolkit to Django[1]. > > I will briefly try to explain why this is necessary. > > When I started to hack around Pootle, I was more or less on my own. > Documentation is very scarce, as there's only one tutorial on jToolkit's web > page [2]. Current developers don't have much time to offer to newcomers, so > the > only way was to dig into source code, browsing back and forth, to get known > with source. > > On the other side, Django is very well documented and it's developer community > is quite big, making it easy to find help when a newcomer is stuck with > framework. It is also more likely for a developer to contribute, if the > project > has good documentation and by using Django, we'd have half of Pootle > documented > very well. Also, Pootle developers now also maintain jToolkit, where if Pootle > moves to Django, framework is maintained by others, leaving current Pootle > developers more time for Pootle. > > I intend to make migration with a set of patches against svn trunk. Maybe it > would even be smart to create a new branch. > > I'm now about 25% done and I've significantly compacted code, making it more > readable. Some of the localization strings have also been moved to templates, > which also makes some code obsolete. > > What is your opinion on this? > Hi
Since I'm the one who originally wrote Pootle using jToolkit, I thought I should comment... Because I wrote most of jToolkit (for my other work), using it meant that I could get Pootle out the door initially without having to learn any new framework. Since that time, I've changed my mind on many of the design decisions that were made for jToolkit (originally it didn't support any templates, etc, which made the code REALLY ugly.). There have been some updates to support templates and make life slightly easier (localizing strings directly within the templates was one of the glaring uglinesses remaining :-)) but I'm now working on a new web framework that revisits these things. Of course, nowadays there are much nicer web frameworks around like Django, and so it makes sense for Pootle to move away from jToolkit. I'm keen to see how this turns out - a branch would be a nice way to test it David ------------------------------------------------------------------------- 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
