![[Trackback URL for this entry]](/nb//themes/Default/tb.png)
2005-06-10T17:14:16 wx vs tk response: The following is in response to a link inside http://cain.supersized.org/archives/44-Python-Tkinter-vs.-wxPython.html
--
http://wiki.wxpython.org/index.cgi/Choosing_20wxPython_20over_20Tkinter has a fair amount of FUD.
"""With Tk you pay ['the price'] later, when you're developing applications with real interface requirements."""
That's very easy to say without justification. UI requirements might be in the form of "we need an HSV color picker", but they also are often in the form of "users must be able to see the status of the multi-step operation, and you have 1/2 day to get that feature done". What is 'real' intended to mean, aside from 'whatever wx is good at'?
"""The downside to this is that Tkinter apps tend to look like misfits on every desktop. I can tell just by looking at a screenshot if a program was written using Tkinter."""
That last claim is often untrue, of course. And, we're hardly at the point where the toolkits are so equal that you can simply choose the one that has the prettiest default fonts and border styles. If you're writing programs where the superficial look and feel is more important than other deeper gui toolkit issues, do whatever you want-- our paths probably aren't going to cross.
