You can update the EGL deployment descriptor
with details that are needed to deploy Rich UI applications.
To add Rich UI deployment details to the EGL deployment descriptor,
do as follows:
- Open the EGL Deployment Descriptor editor by double-clicking
an EGL deployment descriptor.
- Click the Rich UI Deployment tab.
The Rich UI Deployment page is
displayed.
- If you want to deploy all the Rich UI handlers in the project
without dynamic loading and if you accept the default HTML file names,
select Deploy All Rich UI Handlers and proceed
to Step 9
- Clear Deploy All Rich UI Handlers.
- In the highlighted area on the left of
the window, selecting a check box means that when the EGL deployment
descriptor file is deployed, an HTML file is created that includes
all the code necessary to run the related handler.
Note: A
handler might be deployed in multiple HTML files. Leaving aside the
possible use of dynamic loading, consider the following example: A
handler references a second handler by type. That second handler is
in the same HTML file as the first handler regardless of whether an
HTML file is also created for the second handler.
You can
select a single check box or can use the following shortcuts:
- To select all the check boxes, click Enable All.
- To clear all the check boxes, click Disable All.
- You can open the handler code in the EGL editor. To open
one handler, click the handler entry rather than the check box and
then click Open. To open multiple handlers,
do as follows:
- Either press the Ctrl key and click the entries of interest,
or select a contiguous set of names by clicking one name, pressing
the Shift key, and clicking the last name of interest.
- Click Open.
- You can identify the HTML file that receives the JavaScript™ for a given handler.
To specify the file name, click the HTML File Name column and type
the name. The deployment step adds locale detail
to the name, along with the file extension .html.
For example, if you specify myFile.htm and,
as described later, you request an output for the American English
locale, the deployment step creates the file named myFile.htm_en_US.html.
- This step is not available in version .7. If you
selected a single handler in Step 5,
you can specify which handlers the selected handler will download
dynamically:
- In the section at the bottom left, click Configure.
The Configure Rich UI Dynamic Loading page
is displayed. At the left is a list of all the Rich UI handlers on
the EGL build path of the project being deployed. At the right is
a list of all the Rich UI handlers that will be deployed dynamically.
- Use the displayed buttons to move handlers between the
two lists. The terms on the buttons refer to the effect on the rightmost
list:
- Add adds the handlers that are selected
on the left.
- The following buttons let you move a set of handlers that might
be dynamically deployed; then, you can remove those that are not:
- Add Referenced adds handlers that were
referenced by type inside the selected handlers.
- Add All adds all the handlers that are
listed on the left.
- Remove removes the handlers that are selected
on the right.
- Remove All removes all the handlers that
are selected on the right.
- Click Finish.
- In the Locale Settings area, select or clear
check boxes to identify the locales that you want to support for all
handlers.
The list of available locales is derived
from a Rich UI preference, which you can access by clicking Configure.
A second preference specifies which locales are selected by default
on the Rich UI Deployment tab.
Here are
sources of further information about locales: