]>
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++ | |
eaf3cf57 | 9 | application. |
7bf85405 RD |
10 | |
11 | Actually, now that I think about it it might actually work. We | |
eaf3cf57 RD |
12 | just need to move some of the wxWindows initialization stuff out |
13 | of wxpcinit, ensure that __wxStart is not called and that a wxApp | |
7bf85405 RD |
14 | is not created. So this task becomes: Create a test case for |
15 | embedding wxPython in a C++ app. Should also create some helper | |
16 | functions for passing window objects into the Python code, etc. | |
17 | ||
eaf3cf57 | 18 | Test this with M. |
7bf85405 | 19 | |
7bf85405 | 20 | |
eaf3cf57 | 21 | 3. Add significantly to the tests. |
7bf85405 | 22 | |
eaf3cf57 RD |
23 | 4. Derived Python classes should have the ability to call the standard |
24 | On** methods in the base class. | |
7bf85405 | 25 | |
eaf3cf57 RD |
26 | 5. There are some virtual On** and other methods in wxWindows that |
27 | should end up being callbacks in derived python classes, but they | |
28 | are not called via the standard event system. Is there any way to | |
29 | hook into these and call Python methods (if they exist in the | |
30 | derived class) without having to derive a specialized C++ class? | |
31 | ||
32 | 6. Add the Doc/View related classes | |
33 | ||
34 | 7. Add the Printing related classes | |
35 | ||
36 | 8. Document the differences (method signatures, new methods to | |
37 | compensate for no overloading, etc.) between wxPython and wxWindows. | |
38 | ||
39 | 9. Create some larger-scale sample application with wxPython to show | |
40 | it can be done and the simplicity that it will provide... Test | |
41 | distribution with Freeze. | |
7bf85405 | 42 | |
7bf85405 | 43 |