DiaCanvas is a generalized version of the drawing canvas used by DIA. It extends some features used by DIA and adds new ones, while preserving as many of the original features as possible. This project is no longer actively maintained. It is suggested that you try DiaCanvas2 instead.
The JScrollDesktopPane Swing component for Java provides a virtual desktop replete with dynamic scroll bars, dynamic menus, and dynamic button shortcuts. The JScrollDesktopPane class surmounts the limitations of the original JDesktopPane Swing component, offering a solution to the clipping and overlap problems inherit to said component, and mimics the interface of the original JDesktopPane to provide an easy upgrade path. It provides a scrolling MDI desktop, one of the most requested features to the Java JDK.
Glib Binding properties is a system that allows developers to bind properties of GLib and GTK+ objects (Ada95 bindings are also available). This makes it possible to synchronize the properties of several objects, so that when one property changes the properties bound with it automatically change accordingly. This often eliminates the need to write callbacks watching for changes of properties. It supports one-way and mutual bindings and bindings with transformation functions.
libview is VMware's Incredibly Exciting Widgets, a collection of GTK+ widgets used within VMware products. These widgets are the same ones used in VMware Workstation 5.0 and higher, and were considered useful enough to open source so that others could use them in their own projects. These widgets are actively developed and maintained.
GTK ADI Library is a library containing GTK ADI widgets. ADI stands from Advanced Document Interface, and is an MDI (Multiple Document Interface) implementation. It contains a common MDI interface widget and several MDI representations (views). There are currently two views available: a "classical for GTK" tabbed MDI view, and an aligned MDI view. The aligned MDI view can have all child windows visible on the same parent screen, but without wasted space between them as can usually happen when a traditional MDI widget is used. Further development will include a window MDI view, where all the child windows are represented by the standard GTK windows or dialogs.