This addendum gives guidelines and tips for porting applications from version 1.xx of wxWindows to version 2.0.
The first section offers tips for writing 1.xx applications in a way to minimize porting time. The following sections detail the changes and how you can modify your application to be 2.0-compliant.
You may be worrying that porting to 2.0 will be a lot of work, particularly if you have only recently started using 1.xx. In fact, the wxWindows 2.0 API has far more in common with 1.xx than it has differences. The main challenges are using the new event system, doing without the default panel item layout, and the lack of automatic labels in some controls.
Please don't be freaked out by the jump to 2.0! For one thing, 1.xx is still available and will be supported by the user community for some time. And when you have changed to 2.0, we hope that you will appreciate the benefits in terms of greater flexibility, better user interface aesthetics, improved C++ conformance, improved compilation speed, and many other enhancements. The revised architecture of 2.0 will ensure that wxWindows can continue to evolve for the foreseeable future.
Please note that this document is a work in progress.
Preparing for version 2.0
The new event system
Class hierarchy
GDI objects
Dialogs and controls
Device contexts and painting
Miscellaneous
Backward compatibility
Quick reference