Table of Contents
Migrate Pootle away from jToolkit
Since the jToolkit is not under active development anymore, it is necessary to move Pootle to a modern web framework.
Possible alternatives
Current dependencies on jToolkit
- serving web sites
- templates
- session management
- handling of preferences
spell checking(historically)- sending mails
- time based caching
- file locking
- some tests
Migration tasks
- new testing framework (probably rewrite; maybe based on python unittest and Twill)
- integrate a new spell checker
- move non-core features to the translate-toolkit (e.g. merging translations from different sources)
- user preferences (probably connected to the openid project; maybe based on ConfigObj)
- server configuration (maybe with ConfigObj):
- properties of projects and languages
- descriptions
- file locations, …
- web server / application server:
Random thoughts
- the migration of the web server to another framework seems to be the biggest single task - it should be hard to do this incrementally (if that is necessary)
- the inter-dependence of the openid project and the framework migration increases the complexity