a few tweaks

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@595 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn
1998-08-18 19:45:09 +00:00
parent befe54c6ca
commit eaf3cf57ed

View File

@@ -9,26 +9,35 @@ These are the major tasks to be done on wxPython:
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 is not created. So this task becomes: Create a test case for
embedding wxPython in a C++ app. Should also create some helper embedding wxPython in a C++ app. Should also create some helper
functions for passing window objects into the Python code, etc. functions for passing window objects into the Python code, etc.
3. Derived Python classes should have the ability to call the standard Test this with M.
3. Add significantly to the tests.
4. Derived Python classes should have the ability to call the standard
On** methods in the base class. On** methods in the base class.
4. There are some virtual On** and other methods in wxWindows that 5. There are some virtual On** and other methods in wxWindows that
should end up being callbacks in derived python classes, but they are should end up being callbacks in derived python classes, but they
not called via the standard event system. Is there any way to hook are not called via the standard event system. Is there any way to
into these and call Python methods (if they exist in the derived hook into these and call Python methods (if they exist in the
class) without having to derive a specialized C++ class? derived class) without having to derive a specialized C++ class?
5. Add the Doc/View related classes 6. Add the Doc/View related classes
6. Add the Printing related classes 7. Add the Printing related classes
7. Document the differences (method signatures, new methods to 8. Document the differences (method signatures, new methods to
compensate for no overloading, etc.) between wxPython and wxWindows. compensate for no overloading, etc.) between wxPython and wxWindows.
8. 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.