What do you need to configure a Genero Desktop Client (GDC) application?
To add an application for GDC, you need to specify:
- An application Id (a unique name for this APPLICATION element)
Note: Applications defined in the GAS configuration file require an
Id attribute. For external configuration files, if the application and the
configuration file share the same name, there is no need to specify the Id
attribute.
- The parent application from which to inherit configuration details
("defaultgdc" in this example)
- The path to the compiled application files
- The name of the application to launch
- The access control allowing access (optional)
Example: simple configuration for GDC application
In the following example the configuration is for a GDC application defined in the GAS
configuration file.
<APPLICATION Id="my-app" Parent="defaultgdc">
<EXECUTION>
<PATH>$(res.path.fgldir.demo)</PATH>
<MODULE>demo.42r</MODULE>
</EXECUTION>
</APPLICATION>
- The application inherits the configuration settings of its parent ("defaultgdc"
in this example).
- The path used in this example is a RESOURCE; you could also use the absolute path name leading
to your application files.
- The MODULE contains the name of the application to launch.
Example: gdc-demo-external.xcf
This external configuration file would accomplish the same task as the
Example: simple configuration for GDC application that is defined in
the GAS configuration file. The only differences are the lack of the
Id attribute and the
reference to the XML schema.
<APPLICATION Parent="defaultgdc"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://www.4js.com/ns/gas/3.00/cfextwa.xsd">
<EXECUTION>
<PATH>$(res.path.fgldir.demo)</PATH>
<MODULE>demo.42r</MODULE>
<ACCESS_CONTROL>
<ALLOW_FROM>$(res.access.control)</ALLOW_FROM>
</ACCESS_CONTROL>
</EXECUTION>
</APPLICATION>
The
ALLOW_FROM element specifies from what hosts access
is allowed, the example here is defined in a RESOURCE.