[ Thanks to Kevin
Reichard for this link. ]
“So, you’re interested in writing a GTK+ program,
specifically in creating a useful interface between your
application and the user. GTK+ is not the only choice as far as
user interface libraries go–but I’m assuming it’s the choice
you’ve made or you wouldn’t be here reading this article. (If you
are here for any other reason, such as wondering if I’m going to
start a flame war by comparing GTK+ to other libraries, I’m afraid
you’ll be disappointed. This is strictly a how to use GTK+ for
those who are interested.)“
“There are a couple basic concepts you need to be familiar with
before we can proceed to an actual GTK+ program. If you are
familiar with widgets and signals, feel free to skip the first
section and proceed to “Steps to a GTK+ Program.” Otherwise, if you
are brand new to the world of GTK+–forge ahead (no cuts
allowed!).”
“The primary object dealt with in a GTK+ program is a widget. A
widget can be a button, a menu bar, an editor, a file selector, a
scrollbar (well, you get the idea). Even though it’s written in C,
GTK+ is an object-oriented style of library, so concepts such as
classes, instantiation and inheritance apply. Basically, a widget
class defines what the object is and what it does. Since widgets
don’t stand alone, but share attributes with other widgets, it is
simpler to have a hierarchy of widget classes. The hierarchy of a
widget class is shown in its corresponding Reference Document
Project (RDP) page, a document you shouldn’t be without…”