Mark Summerfield wrote:
Signals and slots are used to combine widgets to get particular behaviours, e.g., to only enable an OK button if various fields are filled in, or to repsond to a button click, that kind of thing. Qt's event handling mechanism is used for creating custom widgets.
Yes, I know it's not quite the same thing, but it's an example of the same kind of plug-handler-into-slot programming style. Sometimes it's okay, other times it seems less concise than it could be. PyGUI's action properties actually let you treat it either way -- you can either plug in a handler or have it send an event message. > I know that it is nice creating things from scratch Actually, Qt is the one that's inventing things from scratch. They the advantage that they're implementing everything themselves, so they have total control over how it all works. PyGUI has to work with whatever the platform provides, and sometimes there are severe limitations on the hooks available for doing this kind of thing. A full-blown Qt-like signal-slot mechanism would be a nice thing to have, but it's not easy to build one on top of a system that wasn't designed for it.
PyQt represents a lot of prior art that has proved very durable and popular so I think you'd at least find it interesting to try it out
I have used Qt, but it was a long time ago, and in C++ :-(. I'll take a look some time and see what it's like these days. Need to finish wrestling with printing first, though... -- Greg _______________________________________________ Pygui mailing list [email protected] http://mail.python.org/mailman/listinfo/pygui
