A Python GUI Book.
lac at strakt.com
Mon Nov 12 19:42:33 CET 2001
One defect that most GUI books I am aware of suffer from is that they
are written almost exclusively from the point of view of providing
ways for users to provide _input_ to your program, database, or whatever.
This is easy to teach, and works well with the philosophy that the
user should be in complete control, and that nothing should happen
until the user asks for it, by clicking a button or whatever....
And then, on your first job, you have to write code that handles
real-time updates of a package tracking system. Many people need
to write applications where the user _is_ a passive receiver of
data. This is hard to do well, and worth a chapter all to itself,
in my opinion.
More information about the Python-list