IntelliJ IDEA 12.1.0 Web Help

Some features described here are available in Ultimate edition only.

Use this dialog to create or edit Flash App run/debug configurations which let you run and debug your ActionScript and Flex applications.

Note that this run/debug configuration type is not available for build configurations whose output is a RLM or Library.

Also note that the settings depend on the target platform specified in the associated build configuration (Web, Desktop (AIR) or Mobile (AIR Mobile)).

Name, Build configuration and Override main class fields

ItemDescription
NameUse this field to edit the name of the run/debug configuration.
Build configurationSelect the build configuration to be used.
Override main class Normally, the main application class is defined in the build configuration. If you want a different class to be used as the main application class, select this option and specify the class.

Use browseButton (Shift+EnterShift Enter) to select the necessary class in the Select Main Class dialog.

Optionally, change the application output file name suggested by IntelliJ IDEA in the Output file name field.

Settings specific to Web-targeted applications

ItemDescription
What to LaunchSelect one of the following options:
  • Build output. Use this option to run the generated SWF file using the associated HTML wrapper.
  • URL or local file. Use this option to open a specified URL in a Web browser, or to run a specified local .swf file (either directly or using the corresponding .html wrapper).

    Type the desired URL in the field. Generally, this is going to be something like http(s)://<host>:<port>/<context-root>.

    In the case of a local file, you can use browseButton and select the necessary .swf or .html file in the dialog that opens.

Launch withSpecify the program to be used for running your application. You can use:
  • The system default application, that is, the program associated with the target file type (HTML or SWF) in the operating system. Usually, this is a Web browser. For SWF files, this may also be a stand-alone Flash player.
  • A Web browser.
  • A Flash player.

To select the required program, click browseButton to the right of the Launch with field, and then specify the program in the Launch With dialog:

  • To select the system default application, just click System default application.
  • To select the browser, click Browser and select the required browser from the list.

    Additionally, you can access the Web Browsers dialog to adjust Web browser settings. To open this dialog, use browseButton next to the list.

  • To select the Flash player, click Flash Player and then click browseButton next to the Flash Player field. Then, specify the location of the required Flash player in the dialog that opens.
Use debugger from SDKSpecify the Flex SDK that contains the debugger that should be used. (If you are using a Flex SDK 3 for compilation, a Flex SDK 4 is recommended for debugging.)

If the corresponding SDK is already defined in IntelliJ IDEA, select the SDK from the list. Otherwise, click browseButton (Shift+EnterShift Enter) and add a definition of the necessary SDK in the Configure SDK dialog that opens.

Place SWF file in a local-trusted sandboxIf the Build output option is selected: select this check box if you want to register your application SWF file as trusted.

Trusted SWF files can interact with any other SWF files. They can load data from anywhere, remote or local.

Technically, trusted SWF files are assigned to the local-trusted sandbox.

Settings specific to Desktop-targeted applications (AIR)

ItemDescription
AIR Debug Launcher optionsIf necessary, specify the AIR Debug Launcher options.

Use the same rules as for specifying the program parameters.

Program parametersSpecify the parameters to be passed to the application.
  • Use spaces to separate individual parameters.
  • If a parameter includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg".
  • If a parameter includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\".

Settings specific to Mobile device-targeted applications (AIR Mobile)

ItemDescription
Run onSpecify whether you want to use an emulator or a real Android or iOS device to run or debug your application:
  • Emulator. Select this option to use a built-in emulator. Select the intended target device from the list. The figures shown to the right of the list are the screen characteristics of the selected target device and are just for your information.
    • Screen is the screen size available to your application.
    • Full is the full screen size of the device.
    • ppi (pixels per inch) is the screen pixel density.

    If the necessary device is not present in the list, you can select Other and specify the desired screen parameters in the corresponding fields.

  • Android device. Select this option to run or debug your application using an Android mobile device.

    Note

    • To be able to use an Android device for running or debugging your application, packaging your application for Android must be enabled in the associated build configuration (the Enabled option on the Android tab).
    • Running or debugging an application using an Android device, normally, assumes installing the application package on the target device. For this operation to succeed, the mobile device must be connected to your computer using USB.
  • iOS Simulator. (This option is available only on Mac computers.) Select this option to run or debug your application using an iOS device simulator. In the SDK field, specify the path to the Apple iOS SDK to be used. (The simulator is included in an Apple iOS SDK.)

    You can click browseButton (Shift+EnterShift Enter) and select the SDK installation folder in the dialog that opens.

    Note

    To be able to use an iOS simulator for running or debugging your application, packaging your application for iOS must be enabled in the associated build configuration (the Enabled option on the iOS tab).

  • iOS device. Select this option to run or debug your application using an iOS mobile device. If necessary, enable fast application packaging. (If fast packaging is enabled, the ActionScript bytecode is interpreted and not translated to machine code. As a result, packaging is performed faster but code execution is slower.)

    Note

    • To be able to use an iOS device for running or debugging your application, packaging your application for iOS must be enabled in the associated build configuration (the Enabled option on the iOS tab).
    • Running or debugging an application using an iOS device, normally, assumes installing the application package on the target device. For this operation to succeed, the mobile device must be connected to your computer using USB.
    • If you are using the AIR SDK version 3.4 or later, the application package will be installed on the target device automatically. For earlier SDK versions, you'll have to initiate the installation manually.
Debug on device over For an Android or iOS device: specify how the device will communicate with your computer after the application has been installed and started:
  • Network. Select this option if the device is going to communicate with your computer over the network.

    Note

    Installing the application package on a device requires a USB connection.

  • USB. Select this option if the device will be connected to your computer using USB. If necessary, change the port suggested by IntelliJ IDEA.
ADL options (emulator)For the emulator: if necessary, specify the AIR Debug Launcher (ADL) options.

Use the same rules as for specifying the program parameters.

App descriptor (emulator)For the emulator: specify the application descriptor to be used. The available options refer to the descriptor-related settings in the associated build configuration.
  • as set for Android means the corresponding settings on the Android tab.
  • as set for iOS refers to the settings on the iOS tab.

Depending on the settings in the build configuration, the following cases are possible:

  • as set for Android: <Android support is not enabled>. Generating the descriptor for Android is disabled. Use the Enabled check box on the Android tab if you want to enable the corresponding option.
  • as set for Android: generated. An auto-generated descriptor will be used. If you want a template-based descriptor to be used instead, select the Custom template option and specify the template.
  • as set for Android: <file_name>.xml. The corresponding custom template will be used to generate the descriptor. The <file_name> in this case is the name of the template file that will be used.

The corresponding cases are also possible for the as set for iOS option.

Before Launch configuration options

ItemDescription
Before Launch Specify which activities should be performed before starting the run/debug configuration:
  • Make. If this check box is selected, the project is compiled automatically prior to running or debugging. This option helps you ensure that all changes are included and compiled.
  • Build Artifacts. If this check box is selected, the specified artifacts will be built prior to running or debugging. To define the artifacts to be built, click browseButton and select the desired artifacts.
  • Run Ant target. If this check box is selected, the specified Ant target will be built prior to running or debugging. To define the Ant target, click browseButton and select the desired target.

    To learn more about Ant support, refer to the Ant Support section.

  • Run Maven goal. If this check box is selected, the specified Maven goal will be executed prior to running or debugging. To define the Maven goal to be executed, click browseButton and select the desired goal.

    To learn more about Maven support, refer to the Maven Support section.

  • Show settings. Select this check box if you want the Run/Debug Configurations dialog to be shown every time you launch this run/debug configuration.

Note

The Before Launch actions are performed in the order they appear in the Run/Debug Configurations dialog. Thus, the artifacts are built before running the Ant targets, etc.

Toolbar

ItemDescription
add (InsertInsert)Use this icon or shortcut to create a new run/debug configuration.
delete (DeleteDelete)Use this icon or shortcut to delete the selected run/debug configuration.
copy (Ctrl+DCtrl+D)Use this icon or shortcut to create a copy of the selected run/debug configuration.
settingsClick this button to edit the default settings for run/debug configurations.
arrowUp arrowDownUse these buttons to move the selected run/debug configuration up and down in the list.

The order of configurations in the list defines the order in which the configurations appear in the corresponding list on the main toolbar.

See Also

Concepts:

Procedures:

Language and Framework-Specific Guidelines:

Web Resources: