]>
Commit | Line | Data |
---|---|---|
7bf85405 RD |
1 | wxPython TODO List |
2 | ------------------ | |
3 | ||
4 | These are the major tasks to be done on wxPython: | |
5 | ||
6 | 1. Get it working for wxGTK. | |
7 | ||
8 | 2. Figure out how to do embedding of wxPython in a wxWindows C++ | |
9 | application. | |
10 | ||
11 | Actually, now that I think about it it might actually work. We | |
12 | just need to ensure that __wxStart is not called and that a wxApp | |
13 | is not created. So this task becomes: Create a test case for | |
14 | embedding wxPython in a C++ app. Should also create some helper | |
15 | functions for passing window objects into the Python code, etc. | |
16 | ||
17 | 3. Derived Python classes should have the ability to call the standard | |
18 | On** methods in the base class. | |
19 | ||
20 | 4. There are some virtual On** and other methods in wxWindows that | |
21 | should end up being callbacks in derived python classes, but they are | |
22 | not called via the standard event system. Is there any way to hook | |
23 | into these and call Python methods (if they exist in the derived | |
24 | class) without having to derive a specialized C++ class? | |
25 | ||
26 | 5. Add the Doc/View related classes | |
27 | ||
28 | 6. Add the Printing related classes | |
29 | ||
30 | 7. Document the differences (method signatures, new methods to | |
31 | compensate for no overloading, etc.) between wxPython and wxWindows. | |
32 | ||
33 | 8. | |
34 |