+1 for GTK. It takes a minute to get used to coming from a VB background
(VB spoils people with its easy GUI builder). You write your own signal
handlers with GTK (and other GUI libs also), instead of having it
'auto-created' along with the button when its dropped. You also learn a
lot more. Qt and Wx look good, I just don't have any experience with
them. Glade for GTK is a very good GUI builder, but again, coming from
VB it's not what you think. It only generates a glade file (XML-like
file containing the layout for the GUI), but it's up to you to fill in
the actual code. The process is something like this:
Build a gui with glade and save it.
Load .glade file in your python code. (builder.add_from_file(myfile))
(where builder is a Gtk.Builder())
Grab objects from it. (self.button1 = builder.get_object('Button1'))
(where Button1 is the name of a GtkButton in the glade file.)
Write signal handlers. (def button1_clicked_cb(self, btn):)
(signal names can be defined in glade)
Connect signals (builder.connect_signals(self))
(where self is a class containing the signal handlers)
I'm no expert at it, but I really like using it. There are different
approaches and styles for using Gtk, so don't think my 'process' is set
in stone. Someone else here may have a different view. The great thing
about Gtk is the amount of control you have over everything. Large
projects may require a different style than small ones.
--
- Christopher Welborn <
cjwe...@live.com>
http://welbornprod.com