Python GUIs: Abandoning TkInter and welcoming wxPython?

[lvirden at cas.org]

According to Fredrik Lundh <fredrik at pythonware.com>:
:What native API?  As of 8.0, Tk still emulates all widgets
:except the scrollbar, and use a somewhat ineffective
:X emulation layer for graphics.  AFAIK, they haven't
:changed that in 8.1...

I suspect that Tk features such as these are the native 'api's to which
the original poster was referring.  The following are a few of
the entries from Tk 8.x changes file.


8/22/96 (new feature) There are four new commands for opening common
dialog boxes: tk_chooseColor, tk_getOpenFile, tk_getSaveFile and
tk_messageBox. Native dialog boxes are used wherever available. (IL)

11/7/96 (feature change) Under Windows, buttons and scrollbars now
have native look and feel.  This affects the default class bindings
and the way the some configuration options are interpreted.  Refer to
the widget manual pages for more details. (SS)
*** POTENTIAL INCOMPATIBILITY ***

12/17/96 (feature change) Native Windows labels do not get a focus-ring
border.  (CS)

7/30/97 (feature change) As a result of native menus, you can no
longer drag through a frame of menubuttons on Macintosh and Windows
and have the menus pop down. You can still click on individual
menubuttons and their menus will pop down.  Applications needing to
present a menubar should consider using the new "-menu" configuration
of the toplevel widget to set up menubar which behaves correctly on
Macintosh, Windows and X Windows. (SRP)

10/21/97 (bug fix) Tk did not reset the result after native dialog
modal loops on Window so background events could perturb the dialog
result. (SS)

-- 
<URL: mailto:lvirden at cas.org> Quote: Saving the world before bedtime.
<*> O- <URL: http://www.purl.org/NET/lvirden/>
Unless explicitly stated to the contrary, nothing in this posting
should be construed as representing my employer's opinions.