| <html> |
| <head> |
| <link rel="stylesheet" href="../webroot/stylesheet.css"> |
| <link href="https://fonts.googleapis.com/css?family=PT+Sans" rel="stylesheet"> |
| </head> |
| <body> |
| <h1>Script Archives</h1> |
| |
| Sometimes a script cannot be deployed as a single file. This could be the case when an additional library is needed, data files, image resources or similar data. |
| |
| <p> |
| In such cases a script project can be exported to a <i>Script Archive</i> using a pre-built wizard. Similar to jar files such an archive provides a manifest that denotes the start script within the archive. |
| During execution a temporary project is created in the workspace and thus all additional resources can be accessed as workspace files. |
| </p> |
| <p> |
| To stay independent of the temporary project name or the absolute file location such projects should use the 'project://' uri scheme to access resources. |
| </p> |
| <p> |
| Archives itself are executable scripts that can be used like any other script type. |
| </p> |
| |
| </body> |
| </html> |
