B Tips for Legacy Toolkit Users

If you previously used the Sun Java Wireless Toolkit for CLDC or the CDC Toolkit, the advice in "Quick Start" still applies. Although the user interface is quite different, the project concept is similar.

The following tips apply legacy terms and ideas to the SDK.

• Runtime focus is less on the project and more on device capabilities and the emulation process.

  In legacy toolkits you had to be careful to match the platforms, the APIs, and the capability of the output device. The SDK handles this problem differently, but as described in "Java ME Platforms," you should be sure that the emulator platform is correct and a device profile is selected.

  Clicking the green arrow runs the main project. If no project is set as the main project, clicking the green arrow runs the current project. To set a main project, click the Run menu, select Set Main Project, and select a project from the dropdown menu. Alternatively, you can right-click any open project and select run.

  In the device selector (Tools > Java ME > Device Selector) you can test many devices without changing the project properties. Right-click any device and select Run Project, Run via OTA, or Run JAR or JAD... and select a project, or in the case of running a JAR or JAD, select the application's JAR or JAD file. Only projects that are compatible with the device are shown in the context menu.

• Import applications from legacy toolkits to SDK projects. The installation of the legacy toolkit must exist on the host machine. See "Import a Legacy MIDP Project," "Create a Platform for Legacy CDC Projects," and "Import a Legacy CDC Project."

• Legacy toolkit settings are Application Descriptors in the SDK. Right-click a project and select Properties. Select the Application Descriptor category.

• Legacy toolkit utilities are generally accessible from Tools > Java ME submenu in the NetBeans IDE. For example, the WMA console, the Java ME SDK Update Center and more can be started from the Tools > Java ME submenu.

  For example, select Tools > Java ME > WMA Console in the NetBeans IDE to see the WMA Console output.

• CPU Profiler, Network Monitor, and Memory Monitor utilities can be accessed from the Profile menu or by right-clicking a project and selecting Profile. See Chapter 9, "Profiling Applications," Chapter 10, "Network Monitoring," and Chapter 11, "Monitoring Memory" for information on running these utilities.

• The emulator is familiar, but there are some fundamental differences.

  It is important to realize that the emulator is a remote process, and when it starts it is independent of the build process running in NetBeans. Stopping the build process or closing a project does not always affect the application running in the emulator. You must be sure to terminate the application from the emulator. For more on this topic, see "Running a Project" and "Working With Projects."

  In the Wireless Toolkit, you could simultaneously run multiple versions of a device because the toolkit would increment the phone number automatically each time you launched a project. Because the emulator is now a remote process, the phone number is a unique property that must be set explicitly for the device instance.

  The emulator has additional display functionality. See "The CLDC Mobile Emulator."