The "standard" Python Gui Framework.

But many don't like it much.

comes out of TCL

Lion Kimbro helper tool

Oct'2014: Upgrading Python in the course of playing with TankWiki has killed my TkInter, which is needed to run some other script someone gave me. {{{ import Tkinter File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk/", line 39, in import _tkinter # If this fails your Python may not be configured for Tk Import Error: dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/, 2): no suitable image found. Did find: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/ no matching architecture in universal wrapper }}}

This suggested getting Active Tcl from Active State. So I did. Installing it didn't make a difference.

Since I only have that 1 need, I figured out how to run that script from the Command Line, and ripped out the GUI code. Hack!

=== user comments ===

I'm a TkInter fan. Like the Python folks in general, I occasionaly look around to see if I should switch from Tk, and it's usually "not yet". I first started with Tk when it was Tcl-only. The things I like the most about Tk are how easy it is to build reusable windows, frames, or widgets in very few lines of code, the text and canvas widgets, and the ease of handling callbacks (Tk is callback based, not event based). Tk's "object model" (for lack of a better term, it's not OO in the traditional sense) and packing are what seem to make it so easy.

The one thing I haven't liked so much about Tk is that I wish it used Te X style layout rather than its current packing model. --KenMacLeod 15Apr02

Edited: |

blog comments powered by Disqus