RE: newbie question: should I learn TKinter or skip it and learnmoreadvanced toolkit?

From: Andy Baker (
Date: 05/12/04

Date: Wed, 12 May 2004 15:20:40 +0100
To: <>

I started with Tk and dropped it on horror when I realised it had no
muti-column list box. Shame coz it is better documented than anything else.

Next I tried Wx I am on Windows so the dependency issue wasn't a problem and
the install was easy.
There are some great example files and documentation is getting better but
it is rather less Pythonic than I would have liked and you find yourself
reading C++ docs and mentally translating them. Not the kind of thing I got
into Python for!

Which brings us to Wax. I really hope this project takes off as it seems the
perfect solution. It is definitely usable. I am going to use it where I can
and learn enough wx to fill the gaps where Wax doesn't reach. Hopefully when
my Python-fu improves I might even be able to contribute!

I think it should be possible to mix wx and Wax code quite easily although I
am at an early stage of my investigations.

pyQt doesn't look like an option on Windows and pyGTK looks like it is even
less documented than wx although I may be wrong here.

> -----Original Message-----
> From:
> [] On
> Behalf Of Hornberger, Chris
> Sent: 12 May 2004 13:42
> To:
> Subject: RE: newbie question: should I learn TKinter or skip
> it and learnmoreadvanced toolkit?
> First learn crawl, then learn walk. Nature rules, Daniel San.
> --------------------------
> Chris Hornberger
> Blackrock - 302.797.2318
> Card carrying MSDN member since 2004.
> No, really. I've got the card to prove it.
> -----Original Message-----
> From:
> [
> Behalf Of Porky Pig Jr
> Sent: Tuesday, May 11, 2004 7:28 PM
> To:
> Subject: newbie question: should I learn TKinter or skip it
> and learn moreadvanced toolkit?
> I'm in a process of digging into Python, and one of the
> problems I'm having is whether I should spend any time at all
> learning TKinter or skip it and start with more advanced
> staff like wx or QT.
> I have no experience with GUI whatsoever, so anything will be
> a learning experience for me. The reason I've decided to post
> this question is that I see some contradictory information in
> different resources.
> In 'Programming Python', learning TKinter is recommended --
> before you move to more advanced toolkits. The rationale is
> (i) it is built-in and since it is also shared by TCL and
> Perl, it is well-maintained and always in sync with the
> latest version of Python, (ii) it is fairly simple to learn,
> small learning curve, easier to grasp some concepts before
> moving to more comprehensive production quality toolkit such as QT.
> In some other resources TKinter is critisized as not well
> integrated at Python at all, so recommendation is 'not to
> waste your time and start learning GUI with either wx or QT'.
> My intent is *not* to become professional GUI developer, but
> simply to get a handle on it, so if I write some utilities, I
> can provide some nice GUI if required. Yet of course, since
> I'm learning something new, it would be nice to learn it
> 'right from the start'.
> So: should I spend some time or TKinter or simply skip it and
> start learning GUI with something like wx or QT?
> (my background: solid C, enough C++ to understand the OOP
> concepts, Perl, too much of it to my liking, BTW)
> TIA.
> --
> --