Renderer should only be used for GTK+ 2

[wxWidgets.git] / docs / todo30.txt

diff --git a/docs/todo30.txt b/docs/todo30.txt
index f6c46d24ba876c7c955735512fe5f1361d0f343f..d02d035b41d9ab26f9dbf698d1026c7024b136b5 100644 (file)
--- a/docs/todo30.txt
+++ b/docs/todo30.txt
@@ -1,4 +1,4 @@
-Enhancements for wxWindows 3.0
+Enhancements for wxWidgets 3.0

 ==============================
 
 This table contains the brief summary of the issues below. Priority and
 ==============================
 
 This table contains the brief summary of the issues below. Priority and


@@ -18,7 +18,7 @@ C++ Features
 ============
 
 - Namespaces:
 ============
 
 - 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
     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


@@ -32,7 +32,7 @@ C++ Features
     without templates, even if not all of its features would be available then)
 
 - Exceptions
     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
     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


@@ -74,7 +74,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
     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.
      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 +119,7 @@ Modules/Plugins
 Architecture
 ------------
 
 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.
 
 needed. Dependency information between modules is needed. Dynamic Plug-In
 loading and unloading must be compatible with that.
 


@@ -162,7 +162,7 @@ wxMiscellaneous
 - wxLocale Extension (eg Currency)
 - wxStreams review
 - wxURL?
 - 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.
   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.