Writing a Style Sheet

Here is a basic example to start with, which is intended to help you quickly understand how to write style sheets in JViews TGO.

How to Write an Easy Style Sheet

A CSS usually starts with the configuration of the graphic component. The graphic component configuration includes the configuration of the view, the interactor, the adapter and of some other elements in relation to the graphic component. For example, to set a background color in a tree component, you can write:

Tree {
  view: true;
}
View {
  background: orange;
}

Once a graphic component is configured, you can start to set the characteristics of the graphic representation of objects that are to be displayed in the component. In JViews TGO, all objects from the model have the CSS type object.

The following CSS extract shows how to configure objects of the business class Alarm. The complete version of this configuration is in the tutorial in:

where <installdir> is the directory where you have installed JViews TGO.

Normally, the JViews TGO tree component displays objects of a custom class as tree nodes indicated by a default icon and a label. You can specify a different behavior by customizing the graphic representation of these objects: you can set a specific icon and define that the label of the tree node has the value of the identifier attribute. A special character, the commercial at sign (@), informs JViews TGO that it must get the value from the business model. The @ character is used as a prefix of the name of the attribute from the model.

object.Alarm {
    label: @identifier;
}

When you have configured the style sheet, you can load it into the various graphic components with the method setStyleSheets:

//Load the tree component configuration
String[] css = new String[] { "tree.css" };
try {
  treeComponent.setStyleSheets(css);
} catch (Exception e) {
  e.printStackTrace();
}

The CSS is dynamically interpreted, that is, you can load a new CSS configuration in a graphic component without recompiling or relaunching the application.

Changing Declarations

Sometimes, the left part is not used to refer to a property of a graphic object. For example, class is a reserved word that represents the class name of the graphic representation.

JViews TGO defines a set of properties that can be applied to user-defined and predefined business objects to customize their graphic representation.

You can also define your own graphic representation by declaring the class property with your JavaBean class and setting it in the CSS rule, as in the following example.

How to Define Your Own Graphic Representation

object.Alarm {
    class: 'javax.swing.JButton';
    text: @identifier;
    background: blue;
    foreground: yellow;
}

The CSS rule defined in this example states that objects from the business class Alarm are represented by JButton instances that are configured with the properties text, background, and foreground.

Specializing CSS Rules

CSS Class

In JViews TGO, the CSS class corresponds to the business model class.

How to Match a Business Class

Within a selector, the syntax for matching a business class is:

object."ilog.tgo.model.IltObject" {
    label: @name;
}

How to Match a Business Attribute

In the table component, table cells have a specific CSS class that is made up of the business class and attribute (column) names. The syntax for a business attribute is the following:

object."Alarm/identifier" {
    label: @identifier;
}

Matching Object Identifiers

Identifier matching in the selector is used to match a specific business object in the model. It is expressed in the format #id. When you use this type of selector, you can customize each individual business object through the style sheet. However, the benefits of factorization through declarations are lost.

How to Match Object Identifiers

#RJLed0 {
    foreground: yellow;
}

Add this rule to the style sheet to set the foreground color of the object RJLed0 to yellow.

Matching Attribute Values

The syntax for matching attribute values is expressed in the format [att=val]. This syntax allows you to write patterns in the style sheet that are close to the objects in the business model and to test the attribute against a value.

The following example adjusts the background color of the table cells in the column identifier according to the value of the attribute perceivedSeverity.

How to Vary Table Cell Background Color Depending on Attribute Value

object."Alarm/identifier"[perceivedSeverity=0] {
    labelBackground: '#FFFFFF';
}

The Priority of CSS Rules

Declarations that are not overridden are still valid. This mechanism allows you to write default declarations for common objects and to refine customization with rules that apply to more specialized objects in the model by overriding the default declarations.

In the following example, business objects of class Alarm have a label with a yellow background when the attribute perceivedSeverity is 0, and a white background when this attribute has a different value.

How to Customize the Representation of an Object Depending on a Specific Value

object.Alarm {
    label: @identifier;
    labelBackground: white;
}
 
object.Alarm[perceivedSeverity=0] {
    labelBackground: yellow;
}

Debugging a Style Sheet

When styling with CSS, one of the most common problems concerns the order of priority. A rule can be assumed to have a greater or lesser priority than is actually the case. Then, unsuitable declarations are applied. With many rules, it can be difficult to determine which declarations apply to which conditions. Understanding the priority of CSS rules is the most difficult aspect of a large style sheet.

Another common problem is syntax errors in the declarations. If an identifier on the left does not refer to a valid property, it will be silently ignored. If the value on the right is invalid, it may also be ignored by the target object. In both cases, the declaration has no visible effect.

Yet another common problem concerns changes in properties. An event marking a new value may trigger a new rule. When the object in the model reverts to its previous state, the previous set of rules applies. Therefore, the previous set of rules must contain declarations that undo the changes in the properties of the graphic object correctly. For example, if a node switches to an alarm state, a CSS rule will create an alarm decoration. When the alarm state is resolved, the decoration should be canceled by a declaration in the normal set of rules.

StyleSheet {
    styleSheetDebugMask: "DECL_MASK|DECL_VALUE_MASK";
}