wxWindows Roadmap

This page represents current thinking about where wxWindows is going in the near, medium and long-term. It also serves as a schedule for new releases so that both developers and users can know what to expect when, at least approximately.

We are adopting the Linux kernel style of numbering system where odd minor version numbers are development versions, and even numbers are stable versions. For example, 2.1.x are development releases, and the next 'stable' or final release of it would be 2.2.

Bug-fix patches to the stable release (if made) then become point releases of 2.2 (2.2.x) while development continues with wild abandon on 2.3.x until the end of the next development cycle when it is released as 2.4.

Development versions that end up on the FTP site or CD-ROM, as opposed to remaining in the CVS archive, are semi-stable -- i.e. they are checked for compilation and run-time problems, but not as thoroughly as the stable versions.

Note that since the wxWindows effort is voluntary, these are not hard-and-fast deadlines: but we will endeavour to follow them as closely as possible.

Note also that the releases described are for wxGTK, wxMSW and wxMotif ports. wxMac currently follows its own development path but is due to merge with the main code base in November/December. Also, minor snapshot releases for specific platforms may be available at dates convenient to the developers. Finally, this page only shows the things which are still left to do, please look elsewhere to see the complete list of changes between the releases, including the things which are already done.

Schedule

Release 2.4.0 (stable)

Release date: ? Stable version of 2.3.

Very important
- wxMac: make the release together with the other ports
- Fix wxStream::Eof() problems
- wxGTK: GTK+ 2.0 support
Important
- (Unix) implement wx-config as a version and build parameters independent script which would just read the configuration files
- Finish wxFileName
- Make it possible to process the key strokes portably
- Add wxSemaphor, fix wxCondition
Nice to have
- support for text in the wxToolBar buttons
- radio buttons in wxToolBar

Release 3.0.0 (stable)

This release should finally mark the end of support for the antiquated compilers without decent support of the modern C++ features such as templates, exceptions and namespaces. wxWindows containers should be replaced with the corresponding standard library classes and std::basic_string<> should be used instead of wxString.

To-Do List

This is just a collection of the various things which it would be nice to include in wxWindows but which are not actively worked on right now and for which no schedule is fixed yet. If you're interested in helping with wxWindows development, one of the small projects below could be a great way to join the team! Developers: please feel free to add to these, and delete them when they are done.

General

Extend and unify drag and drop handling (e.g. we need to specify multiple drop targets that can handle multiple formats).
Expand the number of controls that can be specified in a WXR file; add constraint specification to WXR syntax and Dialog Editor; add multilanguage support to WXR. May be we'd better change the format completely and replace WXR with XML (providing conversion utility for old files)?
Support for 'skins', perhaps using a set of alternative control and window classes written generically in wxWindows.
Serial and parallel port support.
Modem and telephony support.
Book, tutorial.
More examples.

wxMSW

Windows CE port.

wxGTK

GNOME/KDE integration libraries.