Which GUI Library to Use

[J. Random Hacker]

On Thu, 09 May 2002 22:53:46 -0400, A. Keyton Weissinger wrote:

> Hi Folks,
> 
> I am beginning work on what will likely turn into a fairly large
> GUI-based application and would like your thoughts on which library to
> use:
> 
> A) Tk Only
> B) Tk with Python Mega-widgets or similar (i.e. Tk with some other
> stuff) C) Qt (BlackAdder just announced the incorporation of Qt3 into
> BA) D) wxPython
> 
> I want to get the best combination of easiest to install most feature
> rich and do not have enough experience with the non-Tk libraries.
> 
> Thank you!!!!
> 
> Keyton

Dont forget FXPy.
No one else mentioned it, I wonder why.
FXPy is based on the FOX GUI toolkit which is very nice and lightweight.
The FOX library is of an extremely beautiful design.
I like wxPython, but then again, I don't. wxPython and wxWindows are very
much like MFC, which IMHO is not a good thing unless you're porting an
application from MFC. I don't hate MFC because its Microsoft but simply
because its a shitty design and the only reason to copy it is to give MFC
programs an easy and free port path. The Docview architecture was
originally introduced in the early 90s, many years after the literature
had covered how to do MVC (model-view-controller) correctly, and I don't
thinks its any better.
This is just one example, but I don't think something
being structured like MFC is a good thing.
On the other hand, wxPython has lots of features and its mature. In
addition its quite popular. I think that wxPython is light years ahead of
Tkinter too. Also, the fact that wxPython uses a "native" toolkit for
each port is a nice thing, some people don't like the FOX widgets.

You really can't go wrong with either. You can produce a program that
works with either one which is what really matters.