Run/Debug Configuration: XSLT
This run/debug configuration becomes available, when XPath View+XSLT Support plugin is enabled.
Getting access to the Run/Debug Configuration: XSLT dialog
Make sure the XPath View+XSLT Support plugin is enabled. The plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins.
|Input|| Use the controls in this area to specify the XML file to process and the script to be executed. |
|Output|| Use the controls in this area to configure handling of the script output. |
|Parameters|| Use the controls in this area to create and manage a list of parameters to be passed to the script. |
In this tab, configure additional options that are not commonly required in run configurations.
|Smart Error Handling|| |
|VM Arguments||In this text box, specify optional VM arguments to be passed to the VM where the XSLT script is executed. These can be heap size, garbage collection options, file encoding, etc. If the line of VM arguments is too long, click the button and and type the text in the VM Arguments dialog box, that opens.|
|Working Directory||In this text box, specify the working directory to use. Type the path manually or click the Browse button and select the desired folder in the Working Directory dialog box, that opens. |
If no folder is specified in text box, the working directory will be the one where the XSLT script file is located.
|⌘N||Click this button to add a new configuration to the list.|
|⌘⌦||Click this button to remove the selected configuration from the list.|
|⌘D||Click this button to create a copy of the selected configuration.|
|Edit defaults||Click this button to edit the default configuration templates. The defaults are used for newly created configurations.|
|or||⌃↑ or ⌃↓||Use these buttons to move the selected configuration or folder up and down in the list. |
The order of configurations or folders in the list defines the order in which configurations appear in the Run/Debug drop-down list on the main toolbar.
|Move into new folder / Create new folder||Use this button to create a new folder. |
If one or more run/debug configurations are in focus, the selected run/debug configurations are automatically moved to the newly created folder. If only a category is in focus, an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or the buttons.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|Name||In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.|
|Defaults||This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations.|
|Share|| Select this check box to make the run/debug configuration available to other team members. |
The shared run/debug configurations are kept in separate xml files under
This check box is not available when editing the run/debug configuration defaults.
|Single instance only||If this check box is selected, this run/debug configuration cannot be launched more than once. |
Every time a new run/debug configuration is launched, AppCode checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window.
|Specify which tasks must be performed before applying the run/debug configuration. The specified tasks are performed in the order they appear in the list. |