It also possible to perform headless exports of the Storyboard Design files to the Storyboard Embedded Engine files from a command line or scripting environment.
All of the Storyboard executables will be located in the PATH_TO_INSTALL/Storyboard_Designer/storyboard
directories, though on each desktop platform they are named slightly differently
Windows:
..../Storyboard.exe -application com.crank.gdt.ui.gappexport model=<PathToGDEFile[,PathToAdditionalGDEFile,...]> output=<PathToGAPPFile>
Mac:
..../Storyboard.app/Contents/MacOS/Storyboard -application com.crank.gdt.ui.gappexport model=<PathToGDEFile[,PathToAdditionalGDEFile,...]> output=<PathToGAPPFile>
Linux:
..../Storyboard -application com.crank.gdt.ui.gappexport model=<PathToGDEFile[,PathToAdditionalGDEFile,...]> output=<PathToGAPPFile>
Note: Storyboard requires a display, so to run in a true headless environment a Virtual frame buffer needs to be setup.
Xvfb :1 -ac -screen 0 1024x768x8 export DISPLAY=:1 ..../storyboard -application com.crank.gdt.ui.gappexport model=<PathToGDEFile[,PathToAdditionalGDEFile,...]> output=<PathToGAPPFile>
Where the model
is the full path to the Storyboard Designer model file. In
the situation where multiple GDE model files are being joined together it is a comma separated list of model files where the
first model file will be used for the start screen and the remaining models will be used for additional content. The output
parameter specifies the filesystem path where the Storyboard Engine file will be created and the directory containing that file
will be used to for the additional resource directories (scripts, images and fonts).
If the gde file that is being selected for export does not reside in the workspace that is going to be used by the comman line exporter, then the export configuration must be stored in the project. This is an option that is availble when modifying the export configuration. The following picture illustrates the selection that needs to be made:
Note that the "Configuration Location" option is set to "Project". If the project resides in the same workspace that the command line exporter will be using, the configuration can be stored in either the workspace or the project
By default the exported gapp file will be compacted and not in a readable format. If a more readable format is desired, then the readable
parameter can be passed along the command line such as:
..../Storyboard -application com.crank.gdt.ui.gappexport readable model=<PathToGDEFile[,PathToAdditionalGDEFile,...]> output=<PathToGAPPFile>