...
As of Grouper 2.2, most of the Grouper UI configuration (for the Admin UI, Web UI's, and new Grouper 2.2 UI) is now in grouper-ui.base.properties, and you can override it in grouper-ui.properties. See the Configuration Overlay page for details. Some configuration that you generally will not need to change in upgrading to Grouper 2.2 is in media.properties.
...
Differences in the standard and custom UIs which are due to CSS are listed below:
Feature | Standard UI | Custom UI |
|---|---|---|
Menu | Positioned vertically on left. | Positioned horizontally below logos. Various colour changes. |
Content area | To the right of the menu. | Aligned left and full width. |
'Members' | Blue text on pale background. | White text on grey background. |
Many more CSS classes are applied to elements in the HTML source than are specified in the Grouper stylesheets so a high degree of CSS customisation is possible.
...
Since a Grouper UI page may be constructed from many templates, including dynamic templates, and it may not be easy to determine which ResourceBundle key was used to render text, a mechanism has been created to display debug information. Go to the URl /grouper/populateDebugPrefs.do. You should see a form:
|
The form fields are explained in the table below:
Field | Description |
|---|---|
Enable debug display | Determines if debug information is shown at the bottom of the page. If not selected, none of the other options are active. |
Webapp root for I2mi* | The complete file system path to the standard UI webapp root. |
Webapp root for your site* | The complete file system path to the custom UI webapp root. |
Show resource keys and values at end of page | If selected, any key-value pairs derived from the nav ResourceBundle to display screen text are listed. |
Show resource keys in page rather than values | Instead of seeing the text in the page you will see ?key? |
Show dynamic tiles | If selected, a hierarchy of templates used to construct the page is shown. If a template was loaded dynamically, the view, entity type, chosen key and template name are displayed. |
Executable for JSP editor |
The complete filesystem path to a JSP editor - only use if the server is your working machine!
If the webapp roots above are specified, template names are links which will open the template file in the specified JSP editor.
Remove CSS stylesheet references? | Allows you see the non stylised page - used for checking accessibility in absence of a screen reader. |
*These fields are only required if you wish to link template names to a JSP editor.
...