I have to confess that I haven't used pyQT. I like pyGTK, and for a while it had been my widget set of choice. Here are how I see the differences:
1. The "native" (non X11) widgets under Macintosh OS X don't look good; wx's widgets look fine on OS X in both native and X11 (pyGTK) modes.
2. I've had a really hard time getting a pyGTK package ported to Win32. Like, "put your fist through your monitor" hard. wx seems to work effortlessly on win32
3. In moving from 1.x to 2.0, the gtk widgets changed their naming conventions, which means that I now have to support two different naming conventions in one of my pyGTK programs. In contrast, when wx changed to the wx namespace, the changes were made in a backwards compatible manner.
4. Open GL is frustrating under GTK. The gtk.glarea widget, which I started using, has now been abandoned in favor of the gtk.glext widget, which means that I have to port more code.
5. wxGlade outputs Python code directly, Glade doesn't.
Don't get me wrong, pyGTK has a lot going for it, and for a long time I thought it was going to be *the* player in cross-platform widget sets. But it just doesn't seem like there are very many people who use Macs and Windows and care about GTK, which means that using those widgets on those platforms is risky. I'm famous for betting on the wrong horse in computer standards. I bet on GTK; maybe the wx community should be scared that I think it's cool.
Rick Muller
rmuller@sandia.gov
···
On Thursday, March 25, 2004, at 07:57 AM, Bob Klimek wrote:
Rick Muller wrote:
I'm very very impressed with wxPython. I realize that I've said this before, but I've used almost every Python GUI, and have been pretty frustrated with all of them. wxPython rules.
Rick,
I agree that wxPython is very nice, but I was wondering how in your opinion it compares with pyGTK and pyQT?