Administering the client at a basic level is all done through the configuration xml file. The configuration allows multiple clients with different components depending on the user base of the client.
Contexts
Weave 2.6.8 adds contexts to the Weave configuration. A context is a way to group entities, and other configuration items, so that a Weave client can be restricted to using just a subset of all the available entities.
Layouts
The client is made up of three main parts, the toolbar, statusbar and the main content area. The toolbar is located at the top and the statusbar at the bottom. The administrator is free to move actions and components around the interface in order to customise the environment. The main content area is known as a perspective area, views can be added to a border layout within this area.
...
In this example users will only have access to the property, roads, parks and lights entities, with some additional settings being applied to the property and roads.
Entity selections
By default entity selections are preserved between client restarts, by setting the flag retainSelections to false for the client config the selections will be cleared when the client starts
| Code Block | ||
|---|---|---|
| ||
<client:config id="editing" retainSelections="false">
<!-- you could also set it like this -->
<retainSelections>false</retainSelections>
<!-- The rest of the client config goes here -->
</client:config> |
Icons
You can create custom icons that can then be referred to in the client configuration by creating an icons directory within the ...\weave\platform\workspace directory, then any .gif or .png files within there will be available to use anywhere an iconCls attribute can be set. Note that if the icons directory doesn't exist when the server is started it will need to be restarted before icons are available for use.
...