The project I have been working on for the past week or so is based on wxPython (+AUI) and VTK. Unfortunately the documentation for wxPython, when it comes to all but the most basic things, is minimal... at best... and the bugs seem plentiful (in wxAUI at least).
This has led me to waste several hours on annoying things like sizers not growing when they should and random crashes because I have composting on (wtf right?)... which has made me loose trust in wxPython as a toolkit and I really want... no I need this program to be rock solid. Also reading the saya blog made me realize I am not the only one having problems with wxAUI.
I don't want to imply that wxPython is garbage or anything... it's nice for creating quick and simple GUIs but the severe lack of actual documentation (especially at the fringes) has forced me to evaluate Qt as a possible replacement.
In the principle of measure twice, cut once before jumping into porting code I need to evaluate:
- Event Model
- Common dialogs (e.g. Color Selection, File Open/Save)
- Existence of advanced 3rd party widgets (e.g. Scintilla)
- Ease of writing custom widgets (like: wxPython Transfer Function Widget)
- Existence of Qt ports of example code the app uses (like Python console)
- Ease of integration with 3rd party toolkits (e.g. VTK)
I should also start porting from the bigger pieces (VTK integration) to see if Qt is just as slow as wxAUI when it comes to VTK. Hmm maybe I'll write an article about it... and finally get a Siafoo ranking higher than David.
One could actually use the wxWidgets documentations with wxPython but when it comes to wxAUI there is basically no docs... at all. Yes I could actually post on mailing lists and support forums but that implies waiting for hours or even days for a response. Anyway I still like and will probably use wxWidgets (and wxPython) in the future... just not for this project.