Differences between current version and previous revision of ToolKit.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Wednesday, January 21, 2004 12:56:35 pm | by AristotlePagaltzis | |
| Older page: | version 3 | Last edited on Monday, December 15, 2003 3:02:07 am | by AristotlePagaltzis | Revert |
@@ -4,10 +4,11 @@
A [GUI] ToolKit's main responsibility is to abstract away this event loop in a way that it can be maintained and extended easily. To this end, the different "widgets" (such as buttons, labels, menus etc) of a [GUI] are treated as black boxes. An EventModel is then specified, which defines how events "propagate" across these blackboxes. The EventModel is a large factor in the design of an application's architecture. Different [ToolKit]s tend to use very different [EventModel]s, which can cause a great deal of confusion.
Popular [ToolKit]s include
-* [GTK+
], the GimpToolKit, written in [C] but with bindings for many other languages, is the first choice for most any serious application on Linux and foundation of the [GNOME] DesktopEnvironment
+* [GTK], the GimpToolKit, written in [C] but with bindings for many other languages, is the first choice for most any serious application on Linux and foundation of the [GNOME] DesktopEnvironment
* [Qt], written in and for [C++], is the ToolKit the [KDE] DesktopEnvironment is built on top of
* [Tk], a rather crufty and baroque ToolKit, was originally made for [TCL], but now has bindings for several other scripting languages, most notably [Perl]
* [AWT], the first ToolKit of the [Java] class library
* Swing, a more modern ToolKit that superseedes [AWT] in the [Java] class library
* [Motif], which is only of historical interest anymore
+* LessTif, a [Free] [Motif] clone, barely more interesting
