I've come to this discussion rather late... Most modern GUI toolkits have (or will soon have) the widgets to compete with Tk strengths. The difficult question with a Tkinter replacement is the complete fragmentation of the GUI toolkit "market". I don't believe that you can, today, identify a toolkit that you are sure is going to have widespread support and the longevity needed (in 5 years time you don't want to be in the position you are in today with Tk). I see two alternatives... - make the Tkinter replacement an abstraction layer between Python and the *user's* choice of toolkit. The developer gets a consistent API, and toolkits can be adopted and dropped as fashions change. This is the approach taken by VeePee (http://www.thekompany.com/projects/vp/). - don't bundle Tkinter with Python. At least you then make people think a bit more about what they want from a toolkit and make an appropriate choice - let Tkinter's replacement be found by natural selection. At the very least let's have a more up-front presentation of the different options, strengths/weaknesses etc on the web site. Cameron must be getting bored of pointing people to his toolkit summary. For the record, Qt has a good Canvas widget, Unicode support, user selectable Windows/Mac/Unix look & feel etc, etc. Phil
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4