Run/Debug Configuration: PhoneGap/Cordova
Use this dialog box to create configurations for running and debugging applications developed through integration with the help of PhoneGap, Apache Cordova, and Ionic frameworks and intended for running on various mobile platforms, including Android.
On this page:
- Getting access to the Run/Debug Configuration: PhoneGap/Cordova dialog
- PhoneGap/Cordova/Ionic-specific configuration settings
- Common options
Getting access to the Run/Debug Configuration: PhoneGap/Cordova dialog
Make sure the PhoneGap/Cordova plugin is enabled. The plugin is not bundled with RubyMine, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.
PhoneGap/Cordova/Ionic-specific configuration settings
|PhoneGap/Cordova Executable Path||
In this field,
specify the location of the executable file |
|PhoneGap/Cordova Working Directory||In this field, specify the folder under which the PhoneGap/Cordova/Ionic application files to run are stored.|
From this drop-down list,
choose the command to run. The contents of the drop-down list, depend on the actually used framework, namely,
on the executable file specified in the PhoneGap/Cordova Executable Path field. The available options are:
From this drop-down list,
choose the platform for running on which the application is intended.
The available options are:
|Specify Target||Select this check box to appoint an Android physical or virtual device to run the application on and select the required device from the drop-down list. The list shows all the virtual and physical devices that are currently configured on our machine. See http://docs.phonegap.com/en/edge/guide_platforms_android_index.md.html#Android%20Platform%20Guide for details.|
|Alt+Insert||Click this button to add a new configuration to the list.|
|Alt+Delete||Click this button to remove the selected configuration from the list.|
|Ctrl+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||Alt+Up or Alt+Down||Use these buttons to move the selected configuration or folder up and down in the list.|
|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.|
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, RubyMine 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.