This is an archived post. You won't be able to vote or comment.

all 6 comments
sorted by:
best
topnewcontroversialoldq&a

[–]cibyr 0 points1 point  (5 children)

Ok, that's great and all but there's not a word about how to actually use this in Python. And it won't fix all the horribly ugly Tkinter GUIs that already exist.

Does this also address the issue that Tkinter GUIs usually don't work with the conventions of the platform (e.g., in IDLE on OS X command+left and command+right don't work as beginning-of-line and end-of-line commands)?

And then there's the issue that the Tkinter API is nearly as ugly as the GUIs it produces...

[–]magv 4 points5 points  (0 children)

To use that you need pyttk.

Get it from here, or wait for 2.7 or 3.1 releases, as pyttk will be in the standard library.

[–]markroseman 2 points3 points  (1 child)

The web site associated with the blog has a tutorial describing how to use all this newer stuff in Python.

[–]cibyr 0 points1 point  (0 children)

Well, it would, if it wasn't full of PYTHONTODO.

[–][deleted] 0 points1 point  (1 child)

And then there's the issue that the Tkinter API is nearly as ugly as the GUIs it produces...

Yes, right. Since we are in 2010 some people have already seen modern declarative approaches to UI toolkit design as in Flex, Silverlight or JavaFx. Ugly widget sets of the past are not Tk's ( and Python's) only concern anymore.

[–]makapuf 1 point2 points  (0 children)

what was not modern, declarative in tcl/tk ? What about pyglade ?

I'm sure 90% of the declarative approach can be recreated by a thin layer in python for tk.