Chat now with support
Chat with Support

Foglight Evolve 9.0 - Web Component Tutorial

Using the Web Component Tutorial Tutorial 1: Drag and Drop Tutorial 2: Creating a Dashboard Tutorial 3: Adding a Drilldown Page Tutorial 4: Adding Views Tutorial 5: Using a Grid Tutorial 6: Reports Tutorial 7: Creating a Form Tutorial 8: Renderers Tutorial 9: Adding Questions and Answers Tutorial 10: Sending Messages to Other Users

View components

View components are the visible components in the user interface. Multiple components can be arranged on a page and some components can be nested within others. A view contains both view components and configuration information.

Types of view components:

Containers, such as various layouts, splitters, report generator
Data visualization components, such as charts, tables, gauges, labels, trees
Specialized components, such as RSS feeds

The configuration information includes flow control, contextual inputs, data binding, and query specification.

There are two styles to choose from, a browser, which contains a navigator, or the plain view that presents a simple page without a navigation component.

Pages can be decorated with headers, which may contain:

Breadcrumbs, a page name preceded by other page names, representing the navigation path to the current page
Time region, which may contain:
Timestamp: if no time range is applied to the page
Time Range: if available, applies to all views
Nothing: if multiple time ranges are represented
View menu: Actions you can perform on the view
Help menu: Help contents for all components on the current page
Time Range: Change the time range of the page
View menu: In a browser, causes a switch to a different page

View layouts

The following view layouts are available:

Numerous other layouts are available. The ones listed here are discussed in this tutorial. For information on the other layouts, refer to the Web Component Reference help, which can be accessed from the Help tab located in the browser interface action panel.

Data sources

Data sources encapsulate all that the system knows about the data and yet cleanly separates knowledge of the data from how it is presented.

The data source is organized as a dynamic graph of objects, starting from a root that represents the entire data model.

Objects are defined in the API and are not tied to the creation of any particular Java object.

The implementation of the data source must provide a schema for the objects. The schema can be changed dynamically.

Schema must provide:

Data source queries

The following principles apply to data source queries:

Related Documents