An Introduction to the GIMP Tool Kit
The GIMP tool kit gtk+ is the GUI libraries written for use in the GIMP as an alternative to Motif. (See the GIMP series of articles by Michael Hammel in the November to January issues of LJ.) Although gtk+ was created for the GIMP, it can be used for any GUI application. In fact, recently the gtk+ distribution has been split out from the GIMP distribution in anticipation of the 1.0 release.
Like all GUI tool kits, gtk+ provides a variety of GUI components, a.k.a. widgets. One thing that sets gtk+ apart from tool kits such as Motif is the breadth of the widgets provided. Naturally, all tool kits provide some form of a button widget. gtk+ also provides components such as tabbed notebooks and fully functional color pickers not included in the core widgets of other tools kits. Screen shots are provided in Figures 1 and 2 as examples of the appearance of gtk+ widgets.
Another advantage of gtk+ is that it's not limited to a single language. Even though gtk+ is written in C and was originally intended for use from C, there are bindings to many other languages. Just a few of them are C++, Objective C, Python, Scheme, Perl—the list goes on and on with new additions frequently. Chances are someone has already started on bindings for your favorite language.
Best of all, gtk+ is under the Library GNU Public License (LGPL), so there are absolutely no licensing concerns when writing software.
The GIMP tool kit is made up of three different layers. Each layer has its own distinct functionality and depends on the layers below it. The three layers are:
glib: This is a support library that is of general usefulness in many C programs, even non-GUI applications. Most of its utilities are common data structures, such as linked lists (GList), and convenience functions, to ease porting between Unices, e.g., wrappers around malloc and free (gmalloc and gfree).
gdk: This library is basically a thin layer over Xlib and some of Xt to handle the basics of drawing on the X display and handling X events. Having this library means that applications writers never have to see the underlying X libraries to get work done. This library also contains several useful functions for things like handling timers, polling file descriptors and more.
gtk: This library is the meat of gtk+, where all the GUI elements are defined. This library relies heavily on gdk and glib to do its job.
For someone with experience in C programming, gtk+ should be fairly easy to pick up. The internals of gtk+ use some advanced C features like function pointers and some tricks with structs, but application writers should never need to worry about the internals of gtk+. Naturally, any experience with other GUI tool kits (especially Motif) will make learning gtk+ easier.
For a long time the only documentation of gtk+ was the source code, and the sample application, the GIMP. Fortunately, the gtk+ tutorial at http://levien.com/slow/gtk/ has filled that void.
However, gtk+ is a moving target (still being developed) so be wary. If there's any doubt about the validity of some documentation, always double check it against the source code. And, as always, nothing can beat actually writing code to test an option out.
There is also a mailing list dedicated to discussing gtk+. To subscribe, send mail to firstname.lastname@example.org with a subject of “subscribe email-address”, replacing email-address with your e-mail address.
When learning about gtk+, remember that it is still under development, but it is certainly usable for non-trivial applications, the GIMP, for example. There are still plenty of minor bugs and even a few major ones you'll have to work around. For example, at the time of this writing, the text widget still needed a lot of work. But in the two months or more before anyone will read this article in print a lot can happen. The best place to check on the current status of the gtk+ libraries and to get the source is at http://www.gimp.org/gtk/.
Otto is a developer at Red Hat Software who is currently very busy with the next release of Red Hat Linux. He can be contacted by e-mail at email@example.com.
One Click, Universal Protection: Implementing Centralized Security Policies on Linux Systems
Join editor Bill Childers and Bit9's Paul Riegle on April 27 at 12pm Central to learn how to keep your Linux systems secure.
Free to Linux Journal readers.Register Now!
- Cluetrain at Fifteen
- Getting Good Vibrations with Linux
- Embedding Python in Your C Programs
- New Products
- Memory Ordering in Modern Microprocessors, Part I
- Customizing Vim
- [<Megashare>] Watch Mrs Brown's Boys Movie Online Full Movie HD 2014
- Security Hardening with Ansible
- Tech Tip: Really Simple HTTP Server with Python
- RSS Feeds