-Enhancements for wxWindows 3.0
+Enhancements for wxWidgets 3.0
==============================
This table contains the brief summary of the issues below. Priority and
============
- Namespaces:
- We want to have all wxWindows identifiers in "wx" namespace but provide
+ We want to have all wxWidgets identifiers in "wx" namespace but provide
typedefs/#defines for backwards compatibility. This can be done easily
for the classes and the only real problem are the enums as they would
all have to be duplicated at both the global scope (with "wx" prefix) and
without templates, even if not all of its features would be available then)
- Exceptions
- We are not going to use exceptions in wxWindows itself but our code should
+ We are not going to use exceptions in wxWidgets itself but our code should
become exception safe. This is a very difficult task as it means that no
resource allocations (including memory, files, whatever) should be done
without using a smart pointer-like object to store the result as it is the
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
+- Tidy code and add comments to headers (possibly in
Doxygen/Javadoc style)
In addition to wxCOMPATIBILITY code:
-- wxProperty classes.
-- All wxCOMPATIBILITY (1.X) code.
-- contrib/src/canvas?
- contrib/src/mmedia
- contrib/src/applet?
-- Old wxODBC code
- Dialog Editor
wxMiscellaneous
- wxLocale Extension (eg Currency)
- wxStreams review
- wxURL?
-- a way to tell wxWindows to check for any non-portable usage,
+- a way to tell wxWidgets to check for any non-portable usage,
for a given set of platforms. Sometimes you want to be able
to get away with non-portable usage, and sometimes not.
This is probably way too time-consuming to implement.