Development
From DoonLunacy
Contents |
General information
This page contains information about development of dunelegacy.
Code is available at launchpad.
Parts of this page badly needs to be updated..
Subpages
Ideas & Thoughts
Python
In stead of using libconfig for handling of data, implementing python support might be a better option. This would give more flexibility and be more suitable to move all of game specific parts away from the engine and make it easier for others to write their own modules, contribute etc. This shouldn't become a goal before 0.95 release is done though..
Garbage collection, caching & cpu usage
Currently there's a *lot* of room for optimizing the engine for less cpu usage and a lot of memleaks to be fixed (running doon lunacy under valgrind will give an impression of how bad things really are currently). This should none the less not be prioritized before needed functionality is in place and we're wrapping up for 0.95 release. Reasons for this is that a lot of refactorisation and design decissions needs to be worked out, which would require us to redo a lot of these things later anyways. Also related to this is that python provides some automatic garbage collection which might make things a lot easier, but also a lot different..
Scale2x / Scale4x
Is there a possibility of including pixes scaling like Scale2x?
From the site: "Scale2x is real-time graphics effect able to increase the size of small bitmaps guessing the missing pixels without interpolating pixels and blurring the images."
More info: http://scale2x.sourceforge.net/
Code Parts
- Config File Format
format used for game settings and data configuration - Sprites and Sprite Cache
universal interface to access images from data files
Other Pages
- Code style
single style is easier to read and maintain - Plan
what is to be done - Who works on what
make sure there is no duplicated effort - Information on handling of native data
- TODO list
- Dune2K Dune Editing forum
- Reverse this Dune2 wiki page

