andrew wrote:
> Maybe the best approach is to follow /F's lead with Tkinter3000, and
> reimplement the Tkinter API on top of MFC / GTk+ / Qt. (Er... that
> *is* what Tkinter3000 is, right?)
nope -- at least not initially. the first two steps are a new
Tk glue layer, and an extension API that allows you to write
new widgets in pure Python. also see:
http://w1.132.telia.com/~u13208596/tkinter/index.htm
:::
I have plans for how to take the Tkinter API *and* the new
extension API beyond Tk, but let's save that for another day...
:::
> Can someone articulate why Tk should be replaced?
beats me ;-)
</F>
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