Tinker vs wxPython ?- Opinions/Views

[adina_levin at mindspring.com]

For experienced programmers who are familiar with the basic GUI toolkit
pattern, the Wx code examples are probably pretty obvious.

For new programmers, the Tk tutorials will explain basic concepts such as a
hierarchy of widgets, configuration with parameters, assigning callback
options, and visual layout using constraints, grid, or page positioning.

Wrote my first GUI app last weekend and struggled mightily with Wx, then
gave up -- I wasn't able to pick out the patterns from the sample code.

Then I read through the "Programming Python" chapters on Tkinter, and was
enlightened.

a-liberal-arts-major-who-learns-quicker-from-sentences-than-raw-code


"Peter Hansen" <peter at engcorp.com> wrote in message
news:3C12E168.91F9129A at engcorp.com...
> Roman Milner wrote:
> >
> > Tkinter Pros:
> [...]
> > Tkinter Cons:
> [...]
> > wxPython Pros:
> [...]
> > wxPython Cons:
> [...]
> > Difficult to learn [...]
> > Less stable than Tkinter [...]
>
> I have to disagree with these two.
>
> I was able to create several attractive, simple interfaces
> which looked like I wanted them much more quickly with
> wxPython, and I have never had any stability problems with either.
>
> I found I had to fight with Tkinter at every turn, however,
> to make my interface look like I wanted it to, and often
> had to give up my ideal and go with something rudimentary.
> With wxPython, I pictured what I wanted and created it.
> Studying the demo app code went a long way towards making
> the documentation acceptable.  In fact, I think I would say
> once I learned to use the source examples, I found wxPython
> *better* documented for my needs than Tkinter was.
>
> Clearly this is a case of YMMV...
>
> --
> ----------------------
> Peter Hansen, P.Eng.
> peter at engcorp.com