data.bibliothek.commonLayouts.info.html Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of docking-frames-demo-layouts Show documentation

${project.name} is a demonstration of various layout styles

The newest version!

Originally designed to be a test client, this application now shows how
Common handles the case were a layout is loaded for which not all Dockables 
are available.

The application contains 4 different views:

Testing Environment: This view uses its own CControl and the other 
views can add or remove elements from this control. It represents the part
of an application that the user would see, while the other views represent
those parts which are normally hidden from the user.
Storage: Allows to store and load the layout of 'Testing Environment' 
at any time. The layout can either be stored in 'xml' or in 'binary' format.
Single Dockables: Can be used to add/remove SingleCDockables or
SingleCDockableBackupFactorys to/from 'Testing Environment'.
Multiple Dockables: Can be used to add MultipleCDockables
to 'Testring Environment' or to add/remove MultipleCDockableFactorys.


You can use this application as follows:

Create a more or less sophisticated layout by adding various SingleCDockables
and MultipleCDockables to 'Testing Environment'.
Store the layout in 'Storage'.
Remove none, some or all CDockables from 'Testing Environment'.
Load a layout from 'Storage'.
Add dockables or factories to 'Testing Environment' and observe how Common
tries to put the elements again at their old location.


There are some limitations of which you need to be aware:

Once you choose a format for the layout ('xml' or 'binary') you should
stick with that format. If some part of a layout cannot be read because a factory
is missing, then it remains in its raw format. It is not possible to convert
such a fragment into the other format.
Data about SingleCDockables tends to stick around for a longer period
than data for MultipleCDockables. But in any case: loading a layout with
a missing factory, and then storing the layout again can and will result in
a loss of data.
There are different degrees in how aggressive Common tries to put the elements
back at their old place. This application runs at the highest possible degree.
It is possible to disable the whole recovery system or to do some fine-tuning, 
i.e. only restore a subset of elements.