Web components / Using a gICAPI web component |
When defining a gICAPI web component in a form specification file, you can also provide a sizing policy and define additional properties.
To define an gICAPI web component field, add a form field with the WEBCOMPONENT item type and the COMPONENTTYPE attribute. The COMPONENTTYPE attribute is mandatory when defining a gICAPI web component; it defines the root HTML file name describing the gICAPI web component.
A web component field is typically defined with the FORMONLY prefix, as the data for the field is rarely stored in a database column.
Web components are usually complex widgets displaying detailed information, such as charts, graphs, or calendars, which are generally resizeable. Use the appropriate form item attributes to get the expected layout and behavior. For more details, see Controlling the web component layout.
Since web component field definitions are generic, you must use the PROPERTIES attribute to set specific parameters for the component.
The PROPERTIES attribute can define a list of:
where name is a simple identifier, and where values can be numeric or string literals.
Component properties defined in the PROPERTIES attribute are transmitted to the web component through the onProperty() method of the gICAPI object.
The name of a property defined in the PROPERTIES attribute is converted to lowercase by the form compiler. To avoid mistakes, a good programming pattern is to define properties in lowercase, in both the interface script and in the form definition file. Property names are not checked at compile time, so nonexistent or mistyped properties will be ignored at runtime.
LAYOUT GRID { [wc ] [ ] [ ] [ ] [ ] } END END ATTRIBUTES WEBCOMPONENT wc = FORMONLY.mychart, COMPONENTTYPE = "3DCharts", STRETCH = BOTH, PROPERTIES = ( type = "bars", x_label = "Months", y_label = "Sales" ); END