From: aa8vb at yahoo.com (Randall Hopper)
Date: Wed, 19 May 1999 08:32:14 -0400
Subject: Separating GUI and code
Message-ID: <19990519083214.A320451@vislab.epa.gov>
Content-Length: 1120
X-UID: 1809                                                

William Tanksley:
 |
 |On Fri, 14 May 1999 11:11:47 +1200, Greg Ewing wrote:
 |>You might like to have a look at:
 |>http://www.cosc.canterbury.ac.nz/~greg/python_gui/
 |
 |>It's an attempt at a GUI framework for Python that's
 |>not oriented towards any particular GUI toolkit.
 |>The idea was to implement versions of it on different
 |>platforms, to give people an easier-to-use alternative
 |>to Tkinter for cross-platform GUI Python apps.
 |
 |Why?  We already have wxWindows.
 |
 |No disrespect intended, just curious what it offers that wxWindows doesn't.

     For one thing, Python/Tkinter (& Tcl/Tk) is easier to build, and there
is one coordinated distribution of all of them.

     I didn't get to using wxWindows, so I can't comment on that.  I just
pulled down one of the number of varients of the latest version off the GTK
home page this morning.  configure tripped several times on a stock IRIX
system.  I tweaked a few of these, but nuked it when it refused to use
SGI's stock make.

     Unlike most GNU configure-enabled progs, this one doesn't look at your
system and use what you have.

Randall




