Python GUIs: Abandoning TkInter and welcoming wxPython?
Mikael Lyngvig
mikael at pobox.com
Fri Jul 2 11:27:52 EDT 1999
More information about the Python-list mailing list
Fri Jul 2 11:27:52 EDT 1999
- Previous message (by thread): Python GUIs: Abandoning TkInter and welcoming wxPython?
- Next message (by thread): Python GUIs: Abandoning TkInter and welcoming wxPython?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2 Jul 1999 11:56:10 GMT, lvirden at cas.org wrote: >When I run the Tk test suite on my SPARC, Tk cranks thru creating and >deleting windows as fast as the eye can track. Well, that's good. But I think the key word here is "as fast as the eye can track". That's the core of the problem. A good GUI library should be creating and deleting windows many times faster than any human eye can track. That's definitely not the case with Tk. So far I think I've counted 20 or 21 different, intermediate windows, when I resize my main window after having maximized it. >However, there are reports that the Windows version of Tk, because of its >use of the native window widgets, is noticably slower than the X >implementation. Is that the platform to which you refer? Yes, that's the platform to which I refer. But, no, I don't believe one minute that the native window widgets are the cause of the performance problems. If Tk was using the native widgets, it should be impossible for it, no matter how not-good the design is, to be slow. Even a batch file (the pathetic script language that's part of Windows by default) should be able to draw any given native widget fast enough, since its just a question of parsing a few, simple parameters and tossing them to some native code. -- Mikael
- Previous message (by thread): Python GUIs: Abandoning TkInter and welcoming wxPython?
- Next message (by thread): Python GUIs: Abandoning TkInter and welcoming wxPython?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list