The user interface tree defines how the user will see your install when they run it. It contains several install modes that are defined by InstallJammer, and beneath those are the panes that are included for that install mode. Each pane can have any number of actions attached to it.
Common Components
This section of the interface tree is used to hold panes of an install theme that don't belong anywhere in the install process itself. Panes installed in the Common Components section can be modified just like normal panes, but you don't have the option to add the same pane to an install type.
Common examples of this are a background window that covers the screen behind the install wizard with some text or images.
Standard Install
This section contains the panes used by InstallJammer for a standard installation. A standard installation is when the user chooses to install the application just as you built it. All of the panes will be shown in order as they are shown on the interface tree.
Default Install
A default install is when the user has chosen to accept all of your default settings and just do the install without changing anything. The default install usually contains just a few screens to prompt the user to confirm installation and then to copy all of the files.
Console Install
A console install is when the user wants to install the program from a command line instead of through the GUI interface. A console install will run inside a terminal window and everything will be input and output to and from the terminal.
|
|
Console installs are not supported on Windows. |
Silent Install
A silent install is when the user wants to accept all of the default options and install the program silently without a GUI interface. This is useful for some administrators who have to install an application on many different machines.
A silent install does not have any panes, only actions. Because of this, you will only see a list of actions under the Silent Install, and you are not allowed to add panes.
Action Groups
Action groups are a way to group actions together into one place. An action group can contain any number of actions to execute and has its own conditions and properties as well as those of the actions it holds.
Action groups are best used if you define an alias for them so that you don't always have to remember the ID of the action group. This is how InstallJammer sets up the default Startup Actions and Install Actions groups when it creates a new project. You can execute all of the actions in an action group by using the Execute Actions action.