Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

a few tweaks

Browse Source 
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
1 changed files with 23 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
utils/wxPython/TODO.txt
View File

@@ -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++
application.
application.
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.
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.