Understanding wxWidgets development process
First of all, it is useful to know that wxWidgets has stable release branch and a development branch. The stable branch preserves both API and ABI (binary) compatibility between all releases in the same series while the development branches may (and, while, rarely, sometimes do) break API and don't attempt to preserve the ABI at all.
Because of compatibility constraints, the releases in the stable branch generally only add bug fixes and while sometimes new features are also back ported from the trunk (development branch) to them, there are no particular plans for adding new features to stable. So this page describes only the features planned for the next development releases and the next stable release which be done after them.
Please notice that all dates given in the roadmap are very tentative. Due to the nature of open source projects there is no warranty that developers have enough time to make things happen as planned. Being a purely voluntary effort, wxWidgets development doesn't always advance as quickly as we'd like it too -- but your contributions are welcome to speed it up!
Current stable branch: 3.0.x
3.0.0 was released on November 11th, 2013, 3.0.1 on June 15, 2014 and 3.0.2 on October 6, 2014. We plan to make at least a couple more bug fix releases in the 3.0.x series.
Development branch and 3.2
New development happens on 3.1 branch. 3.1.0 was released on February 29, 2016 and we plan to make at least another one, and maybe more, development releases before releasing the next stable 3.2.0.
The main goal for this 3.2 release will be wxAUI refactoring/rewrite with full support for dockable notebook pages.
3.2 will also finally drop support for very old legacy systems (such as Win9x platform) and compilers (MSVC6, maybe MSVC7 as well).
If possible, we'd also like to have the following relatively important features for 3.2:
- Finish and merge wxMaskedEdit implementation. This will require providing support for filtering native controls input on all platforms which would be useful in its own right.
- Support for context-sensitive translations in wxLocale.
- Implementation of "frozen" columns and rows in wxGrid.
- Improve support for window-modal and application-modal dialogs.
but if we can't implement them in time we'll release 3.2 without them.
We don't have any well-defined for 4.0 release yet.
The following items are currently not planned because we don't have the possibility to work on them but would be great to have:
- wxAndroid port.
- wxWinRT port.
Please contact us if you'd like to work on any of these projects -- or perhaps fund their development.