There's a limit to how much xcengine can intuit automatically from a notebook: some form of explicit configuration will be necessary. The most comfortable solution (to avoid introducing another auxiliary file) would probably be to do this in the notebook itself. We could use the currently tagged "params" cell and introduce special handling for a pseudo-parameter (i.e. a variable defined in the params cell) called xce_config. This variable would take a dictionary value containing any amount of XCE configuration options. Initially, it could support a string-valued option ap_name which would set the name of the generated Application Package (thus closing #29 ).
There's a limit to how much xcengine can intuit automatically from a notebook: some form of explicit configuration will be necessary. The most comfortable solution (to avoid introducing another auxiliary file) would probably be to do this in the notebook itself. We could use the currently tagged "params" cell and introduce special handling for a pseudo-parameter (i.e. a variable defined in the params cell) called
xce_config. This variable would take a dictionary value containing any amount of XCE configuration options. Initially, it could support a string-valued optionap_namewhich would set the name of the generated Application Package (thus closing #29 ).