Tips for Legacy Toolkit Users

If you used the Sun Java Wireless Toolkit for CLDC in the past, the advice in Quick Start still applies because although the user interface is quite different, the project concept is similar. These 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 matches project requirements and device capabilities for you, so mismatches do not occur.

  As mentioned in the Quick Start, clicking the green arrow runs the main project. You can right-click any project and select run.

  In the device selector you can test many devices without changing the project properties. Right‐click any device and choose Run. Only projects that are compatible with the device are show in the context menu.

• Import applications from legacy toolkits to SDK projects. The installation of the legacy toolkit must exist.

  See WTK MIDP Project Location.

• Toolkit settings are Application Descriptors in the SDK. Right-click on a project and select Properties. Choose the Application Descriptor category.

• Toolkit utilities are generally accessible from the Tools menu in the SDK.

  For example, the WMA console, profiling tools, monitoring tools and more can be started from the SDK Tools menu.

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

  It’s important to realize that the emulator is now a remote process, and once it has started it is independent of the build process running in the SDK. Stopping the build process or closing a project does not affect the application running in the emulator. You must be sure to terminate the application (the emulator can remain open). For more on this, see Running a Project.

  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 a remote process, the phone number is a property that must be set explicitly for the device instance.

  The SDK provides two unique instances for most devices. For example, DefaultCldcPhone1 and DefaultCldcPhone2 are the same except for the phone number. This means you can perform tests that require two devices (messaging, for example) without customization. If you want to run more than two emulators you can easily make a copy that preserves the settings you require. See Adding a Device Instance.

  The emulator has additional display functionality. See Emulator Options.

Related Information

• Quick Start

• Working With Projects