Maintaining Skins Using Extended Functionality

By default, skins are not used in runtime applications. You can specify and select the skin that is applied to all Jade applications, forms, or controls during the running of an application in the current work session.

You can use Jade skins in applications to enforce a specific skin (for example, a company logo) or the initialization of the runtime application can provide users with the ability to select a preferred skin that is set during the application’s initialize method (by calling app.setApplicationSkin).

The global collection of skins is available to all runtime applications in all systems in your Jade database. In addition, you can enable runtime users to define or maintain Jade skins that you have provided or you can enable them to select from the global collection of skins. For details, see "Selecting a Skin to Use in Runtime Applications".

As references to skins information is contained in the _usergui.dat system schema file, when the ReadOnlySchema parameter in the [JadeClient] or [JadeServer] section of the Jade initialization file is set to true, skins cannot be loaded into a production database.

For details about extracting Jade skins for runtime applications from your Jade Platform development environment, see "Extracting and Loading Skins", in Chapter 9 of the Developer's Reference and to "Specifying Your Schema Options" under "Extracting Your Schema", in Chapter 10 of the Development Environment User's Guide.

You can create your own skin images so that users of the runtime application can maintain the skin definition, if required. For details, "Development Environment Skin Classes", in Chapter 9 of the Developer's Reference.