On Jun 8, 10:22 am, Grant Edwards <inva...@invalid.invalid> wrote: > On 2010-06-08, bart.c <ba...@freeuk.com> wrote: > > Why not: (Pyton ->) Tkinter-API -> Xlib ? > > Because maintain a set of Python bindings for Tk would be a lot more > work.
That would be Tk-API. Tkinter-API means write a GUI toolkit that has the same API as Tkinter, which is s Python module. So he suggests a native Python toolkit (written as Python code or a C extension or both), that can serve as a drop-in replacement for Tk-inter, that bypasses Tcl and Tk altogether. In the absense of other factors, it probably is better for an interpreter for a language that claims to be a powerful for general- purpose applications not to run another general-purpose interpreter to do a common task like GUI. Those other factors aren't absent though. Carl Banks -- http://mail.python.org/mailman/listinfo/python-list
