> [Bill Janssen proposes we use Greg Ewing's PyGUI as the standard GUI > framework in Py3K.]
I really like PyGUI. I have dabbled in a number of different GUI frameworks over the years, and PyGUI is the only one where upon reading the documentation I immediately thought "that's Pythonic!". (It's usually more like "My GOD that's inelegant!".) But PyGUI is not complete. (Greg is one of the people who says this.) And I belive that it is just not ready to be the "blessed" Python GUI framework. Perhaps after a few years more work it will be... and then I would favor including it. But not now. By way of illustration, the GUI task I am working on at the moment is a tree-view in which individual items and entire branches can be selected by clicking checkboxes -- a challenge to most any framework I know of. It's not that PyGUI's tree-view component isn't flexible enough, PyGUI doesn't even *have* a tree view component. Me, I nearly always use wxPython (which is TERRIBLE to use, but it usually does what I need). Besides, including PyGUI doesn't need to be part of Py3K because it doesn't break backward compatibility -- it can be added (if desired) whenever PyGUI is deemed ready. What needs to be decided for Py3K is whether to DROP support for TK. I am actually mildly in favor of dropping TK support in the core if we can make it easy enough to download and install separately. -- Michael Chermside _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
