rebake after libtiff changes

[wxWidgets.git] / docs / todo30.txt

diff --git a/docs/todo30.txt b/docs/todo30.txt
index 506b3b4871f619b5001501df3d3d4f891993debf..07c689df1a72ace8471b9ab51c30a2784eebe1a4 100644 (file)
--- a/docs/todo30.txt
+++ b/docs/todo30.txt
@@ -54,12 +54,11 @@ Core
     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.
+- remove wxCOMPATIBILITY
+    wxDEPRECATED() should be used with everything inside WXWIN_COMPATIBILITY_2_4.
+    The stuff inside WXWIN_COMPATIBILITY_2_6 probably should not be deprecated
+    (yet?) because this would give thousands of warnings for the existing code.
+    Exception is api documented as obsolete in 2.6 release already.
 
 - Modularization/Build System
     Candidates for components:
@@ -74,7 +73,7 @@ Core
     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
+     which allows you to navigate easily among 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.
@@ -119,7 +118,7 @@ Modules/Plugins
 Architecture
 ------------
 
-We aim to arrive at a lazy initializiation of modules only when they are first 
+We aim to arrive at a lazy initialization of modules only when they are first 
 needed. Dependency information between modules is needed. Dynamic Plug-In
 loading and unloading must be compatible with that.