Back to Contents | GAS Configuration File Overview

Web Application Theme Component - Configuration Reference

A theme component defines the theme that an application or set of applications can use. A theme is made up of one or more templates, which are required when a window or form is to be opened using a specified style.  The name of the style is matched with the name of a template; if no template exists for the specified style, the default template is used.

For more information on how templates are used by the Front End clients, refer to How Templates Work.

WEB_APPLICATION_THEME_COMPONENT

The WEB_APPLICATION_THEME_COMPONENT element specifies the theme (set of templates) that the application or set of applications can use. It takes an attribute Id, which specifies the unique identifier for this Template component. It is this unique identifier that is referenced by a Web application to make accessible the list of templates defined therein.

Syntax

<WEB_APPLICATION_THEME_COMPONENT Id="compId" >
   [ <TEMPLATE Id="tplId" > path </TEMPLATE> ]  [...]
   [ <SNIPPET Id="snipId" > snippath </SNIPPET> ]  [...]
</WEB_APPLICATION_THEME_COMPONENT>

Notes

The WEB_APPLICATION_THEME_COMPONENT can contain the following element (described below):

  1. Zero or more TEMPLATE elements (optional).
  2. Zero or more SNIPPET elements (optional)

Example

<WEB_APPLICATION_THEME_COMPONENT Id="cpn.theme.default.gwc">
  <TEMPLATE Id="_default">$(res.theme.default.gwc.template)</TEMPLATE>
  <TEMPLATE Id="_end">$(res.theme.default.html.end)</TEMPLATE> 
  ...
</WEB_APPLICATION_THEME_COMPONENT>

Back to the top

TEMPLATE

The TEMPLATE element associates a template identifier (or style name) with a template to be used in the application. With Genero, you can specify that a window or form be displayed using a specific style.  This style name is matched to a template identifier, and the associated template file is then used to format the display.

Pre-defined template identifiers include:

Template Identifier Description
 _default Default template used when the style attribute of the window is not defined or if the corresponding id is not found.
 _end Template used after the application has closed.
 _error Template used whenever an error occurred.
 _timeout Template used after a USER_AGENT timeout.
 _transaction Template used between two states if the transaction takes too much time to achieve (a REQUEST_RESULT timeout).
 _launch Template used when launching an application (when a RUN instruction launches an application).
 _ft Template used for file transfer secondary page.

Syntax

   <TEMPLATE Id="tplId" > path </TEMPLATE>

Notes

  1. tplId is the template identifier
  2. path is the path to the template file

Usage Examples

  <TEMPLATE Id="_end">$(res.theme.default.html.end)</TEMPLATE>
  <TEMPLATE Id="style1">/home/styledir/style1.html</TEMPLATE>

Back to the top

SNIPPET

The SNIPPET element associates a snippet object identifier with a template to be used by the Genero Web Client snippet-based rendering engine when rendering forms that include the specified object.

Syntax

   <SNIPPET Id="snipId" Style="mystyle"> snippath </SNIPPET>

Notes

  1. snipId is the object identifier
  2. mystyle is the value of the STYLE attribute
  3. snippath is the path to the template snippet file

Usage Example

  <SNIPPET Id="Edit" Style="FileUpload">$(res.path.tpl.ajax)/FileUpload.xhtml</SNIPPET>

Code Example

  EDIT f01 = formonly.f01, STYLE="FileUpload";

For more information, refer to the Genero Web Client Manual.

Back to the top