WxPython versus Tkinter.
rantingrick
rantingrick at gmail.com
Tue Jan 25 11:46:30 EST 2011
On Jan 25, 9:29 am, rusi <rustompm... at gmail.com> wrote:
> Just trying to sift the BS from the real issues
>
> Heres a list of the issues relating to GUI toolkits
Finally someone who knows what the argument is really about! Thanks
rusi!
> Look
There is no doubt wxPython has better look and feel. (+1 wx)
> Nativity-1 (as in apps look like other apps on the OS)
Again (+1 wx)
> Nativity-2 (as in uses 'bare-metal' and not a separate interpreter)
Well Tk uses a separate interpretor so (+1 wx)
> Themeing (ttk)
Yes Tk has themes now. Not sure about how useful they are and what wx
offers so (+0 both)
> Efficiency (extra interpreter)
Well wx is by far more efficient (+1 wx)
> Cross Platform
Wx is cross platform but has some warts. We need to create an
abstraction API to insulate the new users from segfaults and make wx a
safe cross platform GUI so (+1 Tkinter)
> Stability (crashes on some OSes)
Wx is stable but does has some warts as is. (+1 Tkinter)
> Programmability
Wx needs a better API whereas Tkinter is ok (+1 Tkinter)
> Accessibility
Well we know Tkinter in not accessable (+1 wx)
> i18n
(+1 wx)
> Availability of gui builder
+0 both
> Licence
Tkinter is completely open source and wx is LGPL. Some find this to be
a problem however i don't (+0 both)
Tkinter: 3
wxPython: 6
More information about the Python-list
mailing list