An applet run/debug configuration enables you to run Java applets using an applet viewer or a Web page and your local browser.
|Name||In this text box, specify the name of the current run/debug configuration.|
|Applet Class||Choose this option to create a configuration profile for running an applet via an applet class.|
|URL||Choose this option to create a configuration profile for running an applet via a Web page.|
|Applet Class||Use the controls in the area to specify the applet implementation class and the applet size.
The area is available after the Applet Class option is chosen.
|Applet Parameters||In this area, specify a set of applet parameters.
This area is available after the Applet Class option is chosen.
|URL||In the URL/HTML File text box, specify the file to invoke the applet from.
Type the path to the file manually or click the Browse button
and select the file in the dialog that opens.
This area is available after the URL option is chosen.
|Policy File||In this text box, specify the location of tje appletviewer.policy file. Because this file is distributed with IntelliJ IDEA, the text box is by default filled in with the standard location. To specify another location, click the Browse button and choose the desired location in the dialog that opens.|
|VM Options for Applet Viewer||In this text box, specify the string to be passed to the VM for executing the applet viewer.
Usually this string contains the options such as -mx, -verbose, etc.
If necessary, click and type the desired string in the VM Options dialog.
When specifying the options, follow these rules:
The -classpath option specified in this field overrides the classpath of the module.
|Use Classpath and JDK of the Module||From this drop-down list, select one of the modules configured in your project. The classpath and JDK of this module will be used to run the applet with the current run configuration.|
|Use Alternative JRE||Select this check box to enable defining another JRE than the JRE used by the current project / module.|
|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
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
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.