Tkinter vs wxPython: your opinions?

[thelazydogsback at my-deja.com]

Thanks for asking this question - I figured it would come up soon (and
probably has in the past, but I'm new here...) Even more thanks for
those who answered - but I have a few questions that I didn't see
raised:

(1) Does one toolkit behave better in a multi-threaded application than
another? In addition to the design of the toolkit, any kit that uses
native widgets has native restrictions on threading and the GUI (e.g.,
only "main" thread talks to the GUI, etc.), so I'd guess that self-draw
GUIs would have a chance of behaving better here. Also OS-threads would
have more issues than stackless "microthreads" where re-entrency would
be the biggest problem (?). When threads spawned from the main thread
need to update GUI state, what is the standard method used? Does wx's
doc/view architecture make this more straightforward?

(2) I assume I could have an app the used both wx & tk at the window
level, but is it possible to host WX inside of Tk, or visa-versa, at
the frame and/or widget level?

(Disclaimer - I've only done the simplist tk experiments, and have only
looked at the wx docs.)

thanks,
mike


In article <3A6F899F.E164F628 at home.com>,
  rwklee at home.com wrote:
> It has to be cross platform between Linux and Windows, so it  seems
that
> my choices are Tkinter and wxPython.
>
> Your experience, thoughts, opinion, on the relative merits and
pitfalls
> of each?
>
> My particular case:  A GUI that has 5 windows max., will incorporate a
> xmlrpc client, will have a python object browser, being able to build
> data entry screens on the fly from a description of an object's
> attributes, programmer not familiar with either toolkit.
>
> Thanks in advance.
>
> - Rick Lee
>
>


Sent via Deja.com
http://www.deja.com/