We still continue to use our own bug tracker, but you can also submit pull requests on Git Hub, if only to test your changes with Travis CI.
Comments Posted on wx Widgets 3.0.2 maintenance release is now available.
Upgrading to it is strongly recommended for all users of the previous 3.0.x release as it bring a lot of bug fixes but remains 100% compatible with 3.0.0, both at the API and the ABI level, and so upgrading to it doesn't require absolutely any changes to the existing applications.
In addition to the fixes, described in more details in the change log, this release also includes a few minor new features, notably a couple of additions to XRC.
Thanks to all the people who have contributed to this release and we hope that you will find it useful and enjoy working with it!
Comments Posted on wx Widgets is now officially on Git Hub!
Most of the documentation has been updated to reflect the switch, but please let us know if we forgot something and there are still mentions of svn anywhere.
It has popular language bindings for Python, Perl, Ruby and many other languages, and unlike other cross-platform toolkits, wx Widgets gives applications a truly native look and feel because it uses the platform's native API rather than emulating the GUI. wx Widgets 3.1.0 has been released today, as planned, and can be downloaded from Git Hub.As usual, please download the sources or binaries if you are using one of the supported Windows compilers (Microsoft Visual C++ or Min GW-TDM) from Source Forge or our FTP mirror.As for the last couple of releases, we provide binaries for the selected Windows compilers (Microsoft Visual C++ and Min GW-TDM) in addition to the source downloads.As always, there were too many new features and bug fixes to list them all here, please see the change log for the fuller list but, briefly, the main changes in this release are: Please notice that while 3.1.0 is officially a "development" version because it is not fully compatible with 3.0.x, the list of backwards incompatible changes is very short, so you shouldn't have any problems updating to this version from 3.0.x in practice, and you're encouraged to try this version out and use it in production in spite of its odd version number.While we were using this repository since quite some time before, it was only a mirror of the main, Subversion, repository hosted elsewhere.
But we have finally left Subversion behind and are now using Git exclusively.