> One way to make it practical to have a Tcl-less Tk is if several of us
> agree to the design and if we share the burdon of maintaining a fork
> of the Tk sources.
> Can we assemble a list of 5 experienced and motivated people who will
> each promise, say, 24 volunteer hours per month for the next six
> months? With anything close to that, I'd bet we could fork Tk
> successfully and usefully. Anyone?
Before you do anything else you might want to look at rivet.
This (according to docs) is a python port of Tk _without_ Tcl (unlink TkInter).
I haven't looked at it yet (downloading now), but if someone else has already
done a lot of the work to separate Tk from Tcl (which I'm assuming this is)
you might want to build on that.
Hope this helps.
James LewisMoss | University of South Carolina | Blessed Be!
firstname.lastname@example.org | | Linux is cool!
"Argue for your limitations and sure enough, they're yours." Bach