Run/Debug Configuration: XSLT
This run/debug configuration becomes available, when XPath View+XSLT Support plugin is enabled.
On this page
- Getting Access to the Run/Debug Configuration: XSLT Dialog Box
- Settings Tab
- Advanced Tab
- Common Options
Getting Access to the Run/Debug Configuration: XSLT Dialog Box
Make sure the XPath View+XSLT Support plugin is enabled. The plugin is bundled with PhpStorm and activated by default. If the plugin is not activated, enable it on the Plugins page of the Settings / Preferences Dialog as described in Enabling and Disabling Plugins.
Use the controls in this area to specify the XML file to process and the script to be executed.
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.
|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.|
|Temporary configurations limit||Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.|
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, PhpStorm 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.
|Before launch||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.