|
Common properties for installer applications are:
-
VM Parameters
If you need to pass special VM parameters to the installer application, you can enter them here.
A common case would be to raise the maximum heap size with a different -Xmx parameter if your installers
require a lot of memory.
-
Arguments
If you need to pass fixed default arguments to the installer application, you can enter them here.
For example, if you want to display a splash screen in unattended mode by default, you can
set the arguuments to -splash "Installing ...". Please note
that command line arguments will be appended to this list, so it is not possible to
"override" a fixed argument from the command line.
-
Custom image for title bar
You can optionally choose a different image for the top right corner of the installer wizard.
This image will be visible for all screens. The recommended size is 60x60 pixels.
-
Window width
Here you can set the initial width of the installer application window. A width of at least 500 is recommended.
-
Window height
Here you can set the initial height of the installer application window. A width of at least 500 is recommended.
-
Resizeable
By default, the installer application window is resizeable, if you would like a fixed window size you can uncheck this option.
-
Add install4j watermark to installer screens
By default, a watermark with the "install4j" product name is added to the divider that separates the navigation buttons on each screen
of the installer application. You can optionally disable this watermark.
-
Look and Feel init script
An optional script to initialize the look and feel. If empty, the system look and feel will be set.
Please note that the look and feel must be available added to the custom code if it is not already part of the JRE.
-
Allow unattended mode
By default, installers allow unattended installations. Please
see the corresponding help topic on installer modes
for more information. All standard actions and standard screens support unattended installations.
If your policy forbids unattended installations or if you include custom code that cannot handle unattended installations,
you can disable them by deselecting this property.
-
Allow console installations
By default, installers allow console installations. Please
see the corresponding help topic on installer modes
for more information. All standard actions and standard screens support console installations,
form screens are also fully mapped to console installers.
If your policy forbids console installations or if you include custom code that cannot handle console installations,
you can disable them by deselecting this property.
-
Fall back to console mode on Unix
On Unix, users often operate in environments where no X11 server is available and no GUI can be displayed. The installer
will fallback to console mode if console mode execution is allowed and this option is selected. Otherwise an error
message will be displayed that tells the user how to invoke the installer in console mode.
-
Default execution mode
By default, an installer application is execution in GUI mode. It is possible to change the default mode to console
mode or unattended mode.
-
Windows console executable
If selected, a console executable will be created on Windows. A non-hideable console will be shown when the installer
is double-clicked in the explorer. This improves the user experience for a console-only installer
(default execution mode set to console) and allows execution through rsh.
-
Console screen change handler
By default, a screen in console mode does not show any particular separation. You insert your own custom display with this script.
The title parameter gives you access to the title of the screen. In console mode, screens display their subtitle only, so the title
string will not be displayed again.
|