1. wxLoad/SaveFileSelector return "wxString" instead of "char *"

[wxWidgets.git] / utils / wxPython / TODO.txt

diff --git a/utils/wxPython/TODO.txt b/utils/wxPython/TODO.txt
index 4f95eb4d54a397038ba2ad5a4cf9a0754f4ecfcd..e0cd903642d60e63d97fd03c8cb235bd0abeba7b 100644 (file)
--- a/utils/wxPython/TODO.txt
+++ b/utils/wxPython/TODO.txt
@@ -6,29 +6,38 @@ These are the major tasks to be done on wxPython:
 1. Get it working for wxGTK.
 
 2. Figure out how to do embedding of wxPython in a wxWindows C++
 1. Get it working for wxGTK.
 
 2. Figure out how to do embedding of wxPython in a wxWindows C++

-application.
+   application.

 
     Actually, now that I think about it it might actually work.  We
 
     Actually, now that I think about it it might actually work.  We

-    just need to ensure that __wxStart is not called and that a wxApp
+    just need to move some of the wxWindows initialization stuff out
+    of wxpcinit, ensure that __wxStart is not called and that a wxApp

     is not created.  So this task becomes: Create a test case for
     embedding wxPython in a C++ app.  Should also create some helper
     functions for passing window objects into the Python code, etc.
 
     is not created.  So this task becomes: Create a test case for
     embedding wxPython in a C++ app.  Should also create some helper
     functions for passing window objects into the Python code, etc.
 

-3. Derived Python classes should have the ability to call the standard
-On** methods in the base class.
+    Test this with M.

 
 

-4. There are some virtual On** and other methods in wxWindows that
-should end up being callbacks in derived python classes, but they are
-not called via the standard event system.  Is there any way to hook
-into these and call Python methods (if they exist in the derived
-class) without having to derive a specialized C++ class?

 
 

-5. Add the Doc/View related classes
+3. Add significantly to the tests.

 
 

-6. Add the Printing related classes
+4. Derived Python classes should have the ability to call the standard
+   On** methods in the base class.

 
 

-7. Document the differences (method signatures, new methods to
-compensate for no overloading, etc.) between wxPython and wxWindows.
+5. There are some virtual On** and other methods in wxWindows that
+   should end up being callbacks in derived python classes, but they
+   are not called via the standard event system.  Is there any way to
+   hook into these and call Python methods (if they exist in the
+   derived class) without having to derive a specialized C++ class?
+
+6. Add the Doc/View related classes
+
+7. Add the Printing related classes
+
+8. Document the differences (method signatures, new methods to
+   compensate for no overloading, etc.) between wxPython and wxWindows.
+
+9. Create some larger-scale sample application with wxPython to show
+   it can be done and the simplicity that it will provide...  Test
+   distribution with Freeze.

 
 

-8.