Version 1.1.2
A screenshot of OrbisGIS, a cross-platform open-source Geographic Information System made by French National Centre for Scientific Research (CNRS).

Version 1.1.1
The Toolbar Extension adds toolbars to the framework. A user can drag and drop each button individually.
The LightTrader from Maxim Golubitsky. This application makes use of the Glass-Extension.
ARMS running on OS X. Chris, the developer, is using NASA's worldwind for the 3D map, JFreeChart for plotting, and JSyntaxPane for XML editing.
Chris has modified DockingFrames such that floating panels have the typical decorations of a dialog. Usually these decorations do not show up.

Version 1.1.0
In version 1.1.0 the theming mechanism was updated. As a result clients can customize the framework even better. In this example a client replaced the algorithm that paints all the components of the framework. Instead of painting a boring gray, the algorithm now paints an image as background. While the contents of the Dockables are not really transparent, they make use of the algorithm as well and thus the background seems to shine through.

Version 1.0.8

With version 1.0.8 the industry has started using DockingFrames. These two images are from IAV, a company working in the field of automotive engineering.
That is also the place where Thomas works, he is responsible for the new glass extension.

Upcoming Version 1.0.8
The old "demo" project gets replaced by a "tutorial" project. This new project contains more, updated, and better explained examples.
Thomas Hilbert wrote an extension adding a fancy looking tab to the EclipseTheme. He also replaced some of the icons.
Tabs can now be placed on all sides. If there is not enough space for all tabs, they are either shown in multiple rows or in an additional popup-menu. Also Dockables not combined with others can now have a tab.

Upcoming Version 1.0.7
Fonts can be set individually.

Version 1.0.6
The default dialog for preferences.

Upcoming Version 1.0.6
Version 1.0.6 will contain a system to manage preferences. The user will be able to modify preferences on a standard dialog or another component supplied by the developer. These preferences can be stored persistent either in XML or as byte-stream.
A preference or an editor can be associated with operations, for example the operation "default" restores the default value of a preference.
While the system comes with a set of default editors and models to handle the preferences that are used in DockingFrames itself, developers will be able to add additional preferences.

Version 1.0.5
With the key combination ctrl + shift + e a popup can be activated, on which the user can choose the focused Dockable.
Another screenshot of the EclipseTheme that is now using its own set of icons.

Version 1.0.4
A screenshot of jUMbLe, made by Andrew McVeigh.

Version 1.0.3
A client using the EclipseTheme.

Version 1.0.2 and below
An application using DockingFrames.
Some noteworthy things on this image:
  • DockActions: some of the panels (Dockables) have little icons on the right side of their title. These are so called DockActions. Some are from the framework itself, some are defined by the application.
  • Stations: the panels are organized in a tree, like java.awt.Component and Container. On the top left is an example: a stack of panels ("Sourcetree", "Database"), together with two other panels ("Source", "Compiler messages") on a "main"-panel.
Several Themes are supported. A theme can change the look and some parts of how the interface reacts on the user. A theme can be exchanged on runtime. Developers can write own themes, ore use existing mechanisms to change the look (and feel).
Another theme using animations and a lot of nice colors.
DockStations are containers for Dockables. A DockStation is like a java.awt.Container, while a Dockable is more a java.awt.Component.
There are different stations with different behaviour:
  • StackDockStation: like a JTabbedPane, only one of several children is visible and can be exchanged by clicking on a "tab". In the image, the panels on the top right "groups.bsrc" and "logic.bsrc" are on a stack.
  • SplitDockStation: like some neested JSplitPanes. All children are visible, and between each child a little gap is visible. The parent of "Source", "Error" and "Sourcetree" is a SplitDockStation.
  • FlapDockStation: shows one or none of its children. Every child is represented by a button, and when this button is clicked, a window opens showing the child. The child "Compiler messages" on the bottom is on a FlapDockStation.
  • ScreenDockStation: shows all of its children in an own window. "Database" is a child of a ScreenDockStation.
DockingFrames has enough flexibility to create some surprising effects. The panel "Open Views" shows a title (a "DockTitle") for each open panel. The theme is respected, and the titles are fully integrated. They can be dragged, their buttons pressed, etc...