PAGE blocks each describe
one dialog page for the
WarpIN installation process. The user switches between the pages by using the
buttons on the bottom of the WarpIN window. WarpIN uses decimal indices to
identify the different pages and to switch between them.
This can only be specified at the root level in the script, i.e. in the
WARPIN block.
See the "Installation Scripts"
page for an overview where this element should be placed.
Syntax:
<PAGE
INDEX="i"
TYPE="{TEXT|README|CONTAINER|CONFIGURE}"
>
<TEXT> ... </TEXT>
[<README ...> ... </README>]
<!-- if TYPE=README -->
[<NEXTBUTTON ...> ... </NEXTBUTTON>]
<!-- if non-standard or last button -->
</PAGE>
In between the <PAGE> and </PAGE> tags,
you must specifiy the text which is to be displayed, using the
<TEXT> ... </TEXT> elements.
Note that regardless of the TYPE attribute,
all pages allow you to specify text in addition to the controls
which are displayed by WarpIN.
Attributes:
INDEX="i"
NEXTBUTTON element description).
TYPE="{TEXT|README|CONTAINER|CONFIGURE}"
type must be
one of the following:
TEXT: This is a text-only page. It has no other functionality
than to display some text.
TEXT pages are optional,
but strongly recommended for introductory information
on the first page. You can specify as many TEXT pages as you like.
A TEXT page must contain a single
TEXT element only. The text
will expand over the entire page.
README: This is a text-only page too, but as opposed to the
TEXT type, this displays both a static introductory text
(specified with the TEXT block, as usual)
plus a README block, which displays
additional, possibly formatted text in a multi-line entry field.
This page type is recommended for displaying a licence agreement or other
README information.
As a result, a README page must contain both a single
TEXT element and a single
README element.
You can specify as many README pages as you like.
CONTAINER: This is the "container" page, which lists the packages
contained in the archive (described by the
PCK elements) in a
container tree view and allows the user to specify installation parameters such as
which packages should be installed and where.
A TEXT page must contain a single
TEXT element only for an
introductory text above the container.
There must be exactly one CONTAINER page in the script.
The next page should be the CONFIGURE page.
CONFIGURE: This is the "system configuration" page,
which allows the user to specify what changes should be made to the
OS/2 system configuration. This page also has the "Create response file..."
button, which allows the user to save the package and configuration information
in a WarpIN response file for CID installation. You should therefore always
specify a CONFIGURE page, even if there's nothing to configure.
Even though a CONFIGURE page is optional,
it is the only way that WarpIN can do the following:
PCK elements in the script.
When turning to the CONFIGURE page, WarpIN automatically determines
from the data of the selected packages whether configuration is neccessary at all.
If so, checkboxes
are displayed to allow the user to prevent WarpIN from modifying the system
configuration.
A TEXT page must contain a single
TEXT element only for an
introductory text above the container.
On this page, the NEXTBUTTON
element should have the INDEX="0" attribute so that after this page,
the actual installation will start.
Alternatively, after the CONFIGURE page, you can display another
TEXT page again, which must then have the INDEX set to 0.
TEXT page saying hello;
README page displaying the license agreement for your product;
CONTAINER page with the packages;
CONFIGURE page.