Movatterモバイル変換

Tkinter and wxPython

• Previous message (by thread):Tkinter and wxPython
• Next message (by thread):Tkinter and wxPython
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi folks,I have seen the GUI wars here, and have for the most partignored them. I am now in a situation where I need input.We have a project that involves a simple GUI--at the moment--that will be getting significantly more complex as the summergoes on.Before we get to far in the project I'm trying to consider myoptions. Here's our analysis so far:Tkinter-------Defacto standardFaster to codeEasier to layout complex screensProven (we know it works)on the down side, it feels slow.wxPython--------Looks significantly betterMore robust widget setfeels fasterThe author works two blocks away (Hi Robin!)on the down side, it is unproven and is not the defactostandard.So, I'm looking for people that have changed projects from onetoolkit to the other and the reasons why they changed.Any insight would be greatly appreciated.Thanks.-- Stand Fast,    tjg.Timothy Grant                                www.hyperlinq.net Chief Technology Officertjg at hyperlinq.net HyperLINq Technologies, Inc.                <>< (503) 246-3630>>>>>>>>>>>>>Linux, because rebooting is *NOT* normal<<<<<<<<<>>>>This machine was last rebooted:  23 days       hours ago<<

• Previous message (by thread):Tkinter and wxPython
• Next message (by thread):Tkinter and wxPython
• Messages sorted by:[ date ][ thread ][ subject ][ author ]