Look & Feel


HAL builds on the default GWT widgets, with minor modifications to provide a consistent look & feel (css references, image bundles, etc)

For specific interaction types we've implemented dedicated widgets, that go beyond what GWT has to offer. I.e. the form input widget that provides an open-save-close model is good example of this.

If a widget has a general purpose then it belongs into the Ballroom library. If a widget only serves our very specific project needs, we keep it within the core/gui module.

Look & Feel

HAL provides two different themes: The default one is the community look&feel used with Wildfly. It's enabled and used out of the box. In order to switch to the product look&feel, you need to rebuild the web console using the -Peap maven profile. This will create a console build that relies on the RCUE styles.

The themes are driven by a Less CSS build step that creates two distinct css file for inclusion with the final console.


The web console implements the W3C Aria specification that defines a way to make Web content and Web applications more accessible to people with disabilities.

The overall layout and each specific widgets are designed to be composed and provide keyboard access and screen reader support across the board.

It is an important requirement to pass the 508 compliance tests. Please keep this in mind when developing new widgets, layout types or navigation concepts.

results matching ""

    No results matching ""