NotSoEasyCoding

From The Battle for Wesnoth Wiki
Revision as of 16:53, 2 February 2007 by Torangan (talk | contribs)

Foreword

This page shows projects which are considered a good idea by the developers but which have nobody working on them so far. If you think you've got the required skill for a task go on, implement it and you've got a high chance that it'll be accepted. The remaining barrier will only be that it's done well. :-)

If you are such a person, you should feel free to edit this page.

If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.

Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.

If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)

Campaign Server related features

Reimplement the campaign server in Perl

The current campaign server is written in C++ and networking with SDL_net isn't really optimal, neither is multithreading easy to do here. Therefore it was proposed to reimplement it in Perl as this should allow for easier inclusion of new features. There are already Perl Modules to read WML.


Integrate WesCamp-i18n into the Campaign Server

So far translations of unofficial campaigns, eras or MP scenarios aren't too easy to handle. Authors must put their stuff into the WesCamp SVN repository, fetch translations from there and put those onto the campaign server. The vision for the future would be that the campaign server will automatically commit every change into the SVN repository and pull translations regulary. This would allow for new translations to appear in the download without further interaction of the authors. Allefant already wrote some Python scripts to handle the SVN commit / fetch part which could be used as external helpers.