Python GUIs: Abandoning TkInter and welcoming wxPython?

[Andrew Cooke]

In article
<64F6457BE0585BB3.1CF2F67BC8A680BD.A19A9FEE23BC9E58 at lp.airnews.net>,
  mikael at pobox.com (Mikael Lyngvig) wrote:
> On 26 Jun 1999 21:37:12 GMT, zeitlin at seth.lpthe.jussieu.fr (Vadim
> Zeitlin) wrote:
>
> > While I don't think wxPython can replace TkInter as a de-facto GUI
standard
> >for Python I still think that it has several advantages compared to
TkInter.
> >Instead of saying how much better, prettier, faster (this one has
really made
> >me smile, BTW: I don't think wxWin is currently very fast, if it has
been
> >cited as its advantage it must really mean that TkInter is extremely
slow.
>
> Well, TkInter is extremely slow, but not because of the Python part.
> Even the Tk widget tour, included with Tk, is so slow that you almost
> think "Please, draw the next character - you can do it." whenever a
> window with some text needs to be redrawn.
>
> In contrast, the wxPython demo is so fast that you probably wouldn't
> realize it is implemented in Python, unless you're used to do GUI
> programming yourself.
>
> One important point is that I probably experience Tk(Inter) as slow
> because I'm used to Win32 desktops with very fast graphics hardware
> and no X/Windows style client/server architecture.  I imagine that
> many X/Windows users experience Tk(Inter) as fast enough.

I'm confused.  I'm sitting at a moderate NT box (266MHz, 96Mb) - my
work machine, and running the Tk demos.  There is no problem at all -
they are instantaneous.

Is this problem to do with memory?  Or is it a W95 thing?  If so,
is it due to thread scheduling?

Andrew



Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.