The sum of the sizes of all of the installed components can be later accessed through the built-in variable $. If 0, then it will automatically be calculated based on the size of the packed files. : Required disk space in the target system. : Whether or not the component can be edited in the component selection page. : Whether or not the component is visible in the component selection page. If the component is not selected, its action lists won’t be executed and its folders won’t be unpacked. : Whether or not the component is selected. This detailed description will be displayed when clicking in the component description in the component selection page. : A detailed description of the component. This description will be included in the list of the visible components presented to the user. You can either start InstallBuilder by double-clicking on it or by invoking the binary from the command line: > /home/user/installbuilder-23.1. This name must be unique and just contain alphanumeric characters and underscores. Whether or not the pattern must match to pass the filter.: Name of the Component. Shortcuts for applications, documents or URLs for Windows Platforms in which this folder will be installedĬonditions that are evaluated and depending on the result, the action is executed, the page associated with the parameter shown or the folder installed This property does not allow variables.Īll, linux, linux-圆4, linux-arm64, linux-arm32, linux-ia64, windows, windows-圆4, osx, solaris-sparc, solaris-intel, linux-ppc, linux-s390, linux-s390x, freebsd, freebsd4, freebsd6, freebsd6-圆4, freebsd7, freebsd7-圆4, openbsd3, hpux, aix, irix-n32 Link to applications, documents or URL for the Windows Start menuįolder name. Shortcuts to be placed in the Windows Quick Launch toolbarĪctions executed right before the file copying step startsĬonditions that are evaluated at build time to decide if the component will be packed. Pages that are displayed to the user through the GUI and text interfacesĪctions executed after the installer has been builtĪctions executed after the installation process has taken place, but before the uninstaller is created and the final page is displayedĪctions executed after the uninstallation process has finishedĪctions executed after the uninstaller has been created and before the installation complete page is displayed.Īctions executed before generating the installer fileĪctions executed directly after loading the project informationĪctions executed before the first page of the installer is displayedĪctions executed before the uninstallation process takes place Language files for customizing the installer translationĭestination folders for the installer filesĪctions executed when the installer has startedĪctions executed if the installation is abortedĪctions executed if a component could not be downloaded and user chose to ignore its installation Java is a fine choice for multiple scenarios and indeed over half of your users use InstallBuilder to package Java-based applications. These were built using the Java programming language. URL to specific component, overrides project’s component URLĪctions executed after the component page, to check that the selected components are a valid combination To fully understand the architecture and capabilities of InstallBuilder, it is useful to consider the previous generation of cross-platform installers. Whether or not the component is visible in the component selection page. Whether or not the component is selected. If 0, then it will automatically be calculated based on the size of the packed files Required disk space in the target system. Whether component should be downloadable. Whether or not the component can be edited in the component selection page.
0 Comments
Leave a Reply. |