-- Use wxEventLoop in all builds.
-- Remove wxCOMPATIBILITY (1.X).
-- Modularization/Build System/Project File Generation.
-- A configuration tool to generate setup.h and configure
- commands.
-- RTTI native Support, Properties/Member-Metadata, 2-Step Init with
- virtual create: e.g. Create(const wxArrayVariant&).
+- use wxEventLoop in all builds
+ wxApp and wxDialog should use wxEventLoop objects (the exact class can be
+ customized by user code by overriding some wxApp::CreateEventLoop())
+ instead of duplicating the same code
+
+- remove wxCOMPATIBILITY (1.X)
+ At least WXWIN_COMPATIBILITY and maybe WXWIN_COMPATIBILITY_2 code should be
+ removed from the library. wxDEPRECATED() should be used with everything
+ inside WXWIN_COMPATIBILITY_2_2. The stuff inside WXWIN_COMPATIBILITY_2_4
+ probably should not be deprecated (yet?) because this would give thousands
+ of warnings for the existing code.
+
+- Modularization/Build System
+ Candidates for components:
+ + contrib widgets (and maybe some of the ones currently in the core)
+ + wxHTML
+ + network stuff
+ + printing (?)
+ + ODBC classes
+ + ...
+
+- Project File Generation
+ We need a (GUI) tool to generate the project/makefiles for all supported
+ platforms/compilers. Not sure if it should be used for the library itself
+ (would be nice to have something like "make menuconfig" for Linux kernel
+ which allows you to navigate easily amon all of the configure/setup.h
+ options but there is a problem with distributing such tool as it can't be
+ compiled by the user because it is needed before the library is built) but
+ we definitely need it for the users makefiles.
+
+- Properties/Member-Metadata, 2-Step Init with virtual create
+ TODO: still unclear what do we need exactly
+
+- Tidy code and add comments to headers (preferably in
+ Doxygen/Javadoc style)
+