Java Reference
In-Depth Information
a vendor connectivity suite; use the SDK emulator utilities that apply to
JSRs used by your application; use on-device debugging with a Symbian
smartphone; add some of your own utilities and, if a very specific need
arises, you might resort to a native Symbian OS tool (e.g., Nokia Energy
Profiler, native CPU profiler or file explorer). Having a variety of tools at
your disposal should help you to develop rapidly for Symbian OS devices.
It is a small thing, but we recommend that you assign one or two days
to learn how to use the tools as early as possible, even before a project
starts. Learning tools requires a certain amount of time, which might
not be available when you get closer to the deadline of a demanding
customer.
To help you apply the above approach, we consider various tools
and discuss their applicability to different needs so that you can make
your own decision on which tool is most suitable for you, in any given
situation.
5.2 Generic SDKs: Java ME SDK 3.0 and WTK 2.5.2
At time of going to print, we are welcoming Java ME SDK 3.0 (see
Figure 5.2). Although it is too early to say farewell to the WTK, which has
been the most popular SDK for quite a few years, let us meet the Java ME
SDK 3.0 and go over some of its features.
Figure 5.2
Java ME SDK 3.0
The Java ME SDK comes with a new underlying architecture and lots
of new features such as:
•
full MSA 1.1 stack
•
integration with third-party emulators and devices
