Build (or update) a XUL application launcher
build-xulapp subcommand [subcommand option(s)] [-uS] [--help] -o <path> [-x <path>] [-t <...>] [[-d] -W <number> -H <number>] [-j <path> --resources <path [ ... ]>] [[-n] --ns-xml-path <path> --ns-xml-path-relative]
--help: Display program usage-o, --output: Output folder path for the XUL application structure-x, --xml-description: Program interface definition fileLocation of the XML program description file. Expect a valid XML file following the http://xsd.nore.fr/program schema-t, --target-platform, --target: Target platformThe argument have to be one of the following:host, linux or osxDefault value: host-u, --update: Update application if folder already exists-S, --skip-validation, --no-validation: Skip XML Schema validationsThe default behavior of the program is to validate the given xml-based file(s) against its/their xml schema (http://xsd.nore.fr/program etc.). This option will disable schema validationsUser interface-W, --window-width: Window widthForce the application main window witdhDefault value: 1024-H, --window-height: Window heightForce the application main window heightDefault value: 768-d, --debug: Add debug console and options into the built interfaceUser data-j, --init-script: User-defined post-initialization scriptA Javascript file loaded after the main ui object initialization stageIf a onInitialize() function is available, it will be called with the main ui object as the first argumentThe script is copied in the chrome/content directory and is available through the following urlchrome://<xulAppName>/content/<xulAppName>-user.js--resources: Additional resourcesA list of path or file to add in the application bundle.These items are copied in the chrome/userdata folder of the application bundle and a new resource url is avalailable (resource://userdata/...)ns-xml options--ns-xml-path: ns-xml source pathLocation of the ns folder of ns-xml package--ns-xml-path-relative: ns source path is relative this program path-n, --ns, --ns-xml-add: Add ns-xml sources into application resourcesInclude the ns-xml library files (sh and xsl) in the XUL application bundle.
Build a Command line interface Python script and its XUL application
build-xulapp python [-s <path>] [-c <...>]
-s, --script: Script to build-c, --classname: Program info class name
Build a Command line interface PHP script and its XUL application
build-xulapp php [-s <path>] [--parser-namespace <...>] [--program-namespace <...>] [-c <...>]
-s, --script: Script to build--parser-namespace, --parser-ns: PHP parser namespaceNamespace of all elements of the ns-xml PHP parser--program-namespace, --program-ns, --prg-ns: PHP program namespace-c, --classname: Program info class name
Build a XUL application which will run a Shell script defined through the bash XML schema
build-xulapp xsh [-p] -s <path> [(-i <...> | -I <...>)]
-s, --shell: XML shell fileA XML file following the XML shell script (XSH) schemaThe file may include a program interface XML definition-p, --prefix-sc-variables: Prefix subcommand options bound variable namesThis will prefix all subcommand options bound variable name by the subcommand name (sc_varianbleNmae). This avoid variable name aliasing.Default interpreter-i, --interpreter: Default shell interpreter typeThe interpreter family to use if the XSH file does not define one.The argument can be one the following :bash, zsh or ksh-I, --interpreter-cmd: Default shell interpreter invocation directiveThis value if used if the XSH file does not define oneThe argument can be one the following :/usr/bin/env bash, /bin/bash, /usr/bin/env zsh or /bin/zsh
Build a XUL application which will run an existing command
build-xulapp command -c <...>
-c, --command, --cmd: Launch the given existing command
Copyright © 2011-2018 by Renaud Guillard (dev@nore.fr)
Distributed under the terms of the MIT License, see LICENSE