LiveContent S1000D customization overview
Using HTML, XML, CSS, and Javascript configuration files, you can customize the LiveContent S1000D user interface (UI).
Control objects within the LiveContent S1000D UI are generated dynamically at runtime, getting their display attributes from resource files you can edit to customize the appearance and behavior of controls.
- is open
- includes graphics
- has preliminary requirements
- is a procedure
When a condition changes, the state of a UI control can change based on the new condition. For example, when moving from a procedure data module with graphics and preliminary requirements to a process data module without graphics or preliminary requirements, the states of the following UI elements change as follows:
- The Next Step and Previous Step buttons change from enabled to disabled.
- The Next and Previous troubleshooting step buttons change from disabled to enabled.
- The graphics-related buttons change from enabled to disabled.
- The Preliminary Requirements button changes from enabled to disabled.
These changes are based on changes in conditions. In this example, the Next Step and Previous Step buttons are enabled when a data module of type procedure is selected. If a data module of type process is selected, the Next and Previous troubleshooting step buttons are enabled. For data modules with graphics, the Display Graphics, Document Only, Graphics Only, and Reorient Text and Graphics buttons are enabled. When a data module includes preliminary requirements, the Preliminary Requirements buttons are enabled.
For each control that can be displayed using different states, there is Javascript code for determining conditions and applying the appropriate state to the relevant elements. Specific code for specific controls can be found across a number of Javascript source files. Some code uses enable and disable methods associated with control objects.