J2ME run/debug configuration options vary depending on the SDK you are using to develop your mobile applications. This section describes the options that are specific for WTK and DoJa, as well as the general options that apply to both SDKs.
|Name||In this text box, specify the name of the current run/debug configuration.|
|Jad/Class/OTA||Select, which of the following sources - Jad, MIDlet class or OTA - is used to be run/debugged. Each source has its own settings described below.|
|JAD||If you have selected to use Jad file as the source for running and debugging, you need only to specify its location in the Jad File.|
|Class Settings||If you have selected to use MIDlet class as the source for running and debugging, specify the following options:
These options can be set, if you have selected to use OTA as the source for running and debugging.
This functionality emulates wireless download of the software from the server.
Therefore, it is necessary to have a working server with such service and the necessary suite (which you want to install and launch) on it.
This service is completely dependent on the emulator vendor and IntelliJ IDEA does not provide it.
So, it should be provided by the emulator or separately by the emulator vendor (for instance, like Nokia does).
Thus, you need to have three items ready - a server, a service and tested suite on that server.
Remember that the actual options list varies from emulator type.
|Jam/Class||Select which of the files, Jam or IApplication Class, is to be run/debugged.|
|JAM||If you have selected to use Jam file as the source for running and debugging, you need only to specify its location in the Jam File field.|
|Class Settings||If you want to use IApplication Class as source for running/debugging, specify its location in the IApplication Class field.|
|Device||Select one of the available devices for the current emulator.|
|Open Preferences||Opens the emulator's Preferences dialog. For more information, refer to emulator's documentation.|
|Open Utils||Opens the emulator's Utilities dialog. For more information, refer to emulator's documentation.|
|Emulator parameters||Type in/edit emulator parameters such as -mx heap_size or traceall.|
|Use classpath and JDK of module||Select a mobile module from the list of modules configured in your project. The classpath and JDK of this module will be used to run your J2ME module with the current run configuration.|
|Alt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+InsertCtrl+N or Alt+InsertAlt+InsertAlt+InsertCommand N or Control EnterControl N or Control EnterCommand N or Control Enter||Click this button to add new configuration to the list.|
|Alt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteCommand Delete or Command BackspaceCommand DeleteCommand Delete or Command Backspace||Click this button to remove the selected configuration from the list.|
|Ctrl+DCtrl+DCtrl+DCtrl+DMeta+DCtrl+DCtrl+DCtrl+D, Ctrl+Shift+Down or Ctrl+Shift+UpCtrl+DCommand DCommand DCommand 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 the newly created configurations.|
|or||Alt+UpAlt+UpAlt+UpAlt+UpAlt+Up or Ctrl+Alt+AAlt+UpAlt+UpCtrl+Alt+UpCtrl+Shift+UpControl UpControl UpControl Alt Up or Alt+DownAlt+DownAlt+DownAlt+DownAlt+Down or Ctrl+Alt+EAlt+DownAlt+DownCtrl+Alt+DownCtrl+Shift+DownControl DownControl DownControl Alt Down||Use these buttons to move the selected configuration or group of configurations (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.
|Use this button to create a new folder.
If one or more run/debug configurations have the focus, then the selected run/debug configurations are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or buttons.
|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.|
|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.
If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate xml file in the .idea\runConfigurations folder if the run/debug configuration is shared and in the .idea\workspace.xml file otherwise.
If the file-based format is used, the settings are stored in the .ipr file for shared configurations or in the .iws file for the ones that are not shared.
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, IntelliJ IDEA 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 make sense, when 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 should be carried out before starting the run/debug configuration.
The specified tasks are performed in the order that they appear in the list.