The Publish feature allows for simple one-button publishing of UJML applications to various target devices and deployment environments. Publish creates the proper files necessary for packaging and deploying UJML applications, making installation on different devices and platforms simpler. 

The SDK includes a set of standard scripts for building UJML applications. Scripts for specific platforms (such as Brew, MIDP, Palm, Microsoft Smartphone, Pocket PC, Symbian, and others) are provided along with the UIE Player for those platforms. Please contact UIEvolution for more information.

Figure 1. Publishing preferences

The SDK includes several build scripts that are useful for creating versions of applications that can be placed on devices. The following sections describe the build scripts that are included with the SDK and their intended purpose. 

Each of these scripts is available within the extensions directory. They can be copied and modified by the user as desired. 

To run one or more publish scripts, click the publishing icon in the toolbar. This runs all active publish scripts. 

Publish scripts are activated and deactivated using the Publish Preferences editor. To open the Publish Preferences editor, click the preferences icon in the toolbar, then select the Publish tab. The Active Project targets list indicates which publish scripts will run when the Publish Icon icon is pressed. Activate and Deactivate targets by selecting them in the Available targets list and pressing the Activate or Deactivate buttons. 

All settings in the Publish tab of the Preferences editor are stored separately for each application directory. The directory chosen by the Application URL in the Select application dialog determines which Publish settings are in use. To change the Application URL, open the Select application dialog by clicking the selection icon in the toolbar.

The Compile script is used to compile UJML source files into UJBC byte code, which is executable by the player. 

The user can choose to turn on or off the generation of trace and debug information in the compilation process. If these features and enabled, there is additional information available when viewing the application in the UJML debugger. These features should be disabled for a production version of an application. 

In addition to compiling UJML source code, this script also copies output byte code and additional files into a specified directory. Additional files are chosen based on file extensions or other wildcards.

The Package script compiles source UJML files and bundles the resultant byte code along with additional image and sound files into a single UIEPK package file. Having a single UIEPK file can simplify the deployment process of an application (note that not all devices are able to use UIEPK files, so this step will not work in all environments). 

When building a UIEPK file, the user can specify which files to include and exclude, either explicitly or through the use of wildcards. It is often helpful, for example, to only include image files of the appropriate image type when building a package for a specific device. 

One additional parameter that needs to be set is the name of the application that should be run initially when the package is launched by the player.

This is a generic script that can invoke any build script. The user specifies the name of the build script.