Department:Programming

The article features all relevant information about the programming department of the project.

Documentation

 * Epydoc for Python code?
 * Doxygen in case we end up writing timecritical C or C++ code?
 * Documentation project files in SVN? (e.g. for Doxygen)
 * Automated daily updated code documentation? Consider server hosting issues. Ask MuteX who already hosts the FIFE documentation.

Editor

 * Nimrod - possible source of inspiration for a PARPG map editor.

Engine

 * Standing on the shoulders of giants: additional libraries that we could utilize?
 * The Feature proposals article contains a list of features that are not present in FIFE yet but would be useful for PARPG development.

i18n

 * When would we need to decide about i18n support? Does it offer any advantage to support it early or would this just be additional work that could also be done later?

Unittesting

 * Unittesting? Test-driven development?

Proposals

 * Coding Standards.
 * Engine requirements.

Drafts

 * Draft:Technical framework.

Python IDEs

 * Extract from here: http://www.gamedev.net/community/forums/topic.asp?topic_id=509478.
 * Any advantage of using one specific IDE on the different supported platforms.
 * IDE project / workspace files in SVN?