Series 40 SDKs: Features

The Series 40 SDKs provide a powerful and comprehensive environment for the development and testing of Flash Lite from Adobe and Java™ applications for Series 40 devices. Combined with your favourite Java IDE, Adobe Flash Professional CS4, or media tools, the SDKs enable development and testing on a PC.

This page provides details of the new features in the latest Series 40 SDK and the key features of the Series 40 SDKs in general.

What’s new in the Series 40 6th Edition SDK?

Location API for J2ME™ (JSR‑179)
The Location API for J2ME™ (JSR‑179) allows developers to acquire location information, listen for changes in location, and identify proximity to a location using a global positioning system (GPS) unit. The implementation also includes features for managing and sharing landmarks.

Location provider
The emulator includes a location-provider utility that makes it possible to provide location or route information to applications. The location provider obtains its route and location information from a formatted text file supplied by the developer.

Advanced Multimedia Supplements (JSR‑234)
The Advanced Multimedia Supplements (JSR-234) API has been updated to version 1.1. This version is a maintenance release that resolves issues with the API.

Force Sensitive Joystick API
The Force Sensitive Joystick API allows developers to take advantage of the navigation keys’ force‑sensor feature, which will be available on selected Series 40 6th Edition devices. The Force Sensitive Joystick API allows an application to determine the direction and magnitude of the force applied by the user to the navigation keys.

Force-sensitive-joystick emulation
The emulator includes a feature that allows developers to test applications that use the Force Sensitive Joystick API.

Flash Lite 3
Support for the Flash Lite Player 3.0 from Adobe is provided. New features include support for Flash Media Server connectivity (RTMP streaming), and enhanced local-file security.

Web browser
The emulator includes the new Series 40 browser, which is based on the WebKit open-source components WebCore and JavaScriptCore. This enables developers to test their sites to ensure that those sites can be browsed easily from the latest Series 40 devices.

Device UI replication
The Series 40 6th Edition emulator implements the UI of the Nokia 6260 slide phone. As such, the look, key layout, key definitions, error messages, display (1:1 pixel ratio), softkeys, and menu selection allow developers to assess how an application will look and behave on a production Nokia 6260 device and, more broadly, on every Series 40 6th Edition device.

Content Packs
Content Packs, collections of copyrighted wallpaper, screensavers, and themes, are available in the emulator. The inclusion of Content Packs enables developers to test applications that make use of this additional copyrighted content. Content Pack items can be used in the emulator only; they are protected against sharing among emulator instances and phones.

Supported IDEs
Development can now be undertaken using the following versions of these popular IDEs:

• NetBeans 6.5 with Java ME pack.
• Eclipse IDE 3.4.1 with EclipseME 1.7.9 or Eclipse Mobile Tools for Java (MTJ) 0.9.1.

Key features of the Series 40 platform SDKs

CLDC 1.1
The SDKs support the connected limited device configuration (CLDC) of Java™ Platform, Micro Edition (Java™ ME) technology. The CLDC specification sets the standard for a highly portable, minimum-footprint Java application platform for connected devices with limited resources. The SDKs implement the specifications in the same way the devices do, providing the closest possible emulation of device behaviour.

MIDP 2.1
The SDKs support mobile information device profile (MIDP) 2.1 APIs, with features such as Mobile Service Architecture (MSA) enhancements, an enhanced security-model, and new domains that expand on MIDP 2.0 features. The SDKs implement the specifications in the same way the devices do, providing the closest possible emulation of device behaviour.

Java™ API
The latest Series 40 SDK supports the following Java APIs:

• Nokia UI API 1.1a with the Force Sensitive Joystick API.
• FileConnection (FC) and Personal Information Management (PIM) APIs in PDA Optional Packages for the J2ME™ Platform (JSR‑75).
• Java™ APIs for Bluetooth (JSR‑82) v1.1, including OBEX support.
• Mobile Media API (JSR‑135).
• J2ME™ Web Services Specification (JSR‑172).
• Location API for J2ME™ (JSR‑179).
• Security and Trust Services API for J2ME™ (JSR‑177), including implementations of the Application Protocol Data Unit (SATSA-APDU) and SATSA-CRYPTO optional packages.
• Mobile 3D Graphics API for J2ME™ (JSR‑184).
• Java™ Technology for the Wireless Industry (JSR‑185).
• Wireless Messaging API 2.0 (JSR‑205) for short message service (SMS) and multimedia messaging service (MMS).
• Content Handler API (JSR‑211).
• Scalable 2D Vector Graphics API for J2ME™ (JSR‑226).
• Advanced Multimedia Supplements (JSR‑234), providing 3D audio and music support.

In addition, through the implementation of JSR‑75, JSR‑82, JSR‑118, JSR‑135, JSR‑139, JSR‑184, JSR‑205, and JSR‑226, the latest Series 40 SDKs provide support for the subset of the Mobile Service Architecture (JSR‑248).

Flash Lite Player
Support for the Flash Lite Player from Adobe is provided, allowing Flash developers to test their applications in the emulators.

Web browser
The new Series 40 browser, based on the WebKit open-source components WebCore and JavaScriptCore, is included in the emulator. This enables developers to test their sites to ensure that those sites can be browsed easily from the latest Series 40 devices.

File formats
The emulators can display the content of messaging, browser, image, calendar, contact, audio, and video files. Support is also provided for displaying streamed audio and video. This allows content to be validated without the use of a device.

Image capture
The emulators can simulate the capture of a still image by a device’s camera, returning a predefined image. This enables developers to test applications that capture still images.

OMA DRM 1.0
The SDKs support the emulation of OMA DRM usage rights on Java applications and mobile media content. This allows developers to confirm that their rights are protected before they release an application or content item.

Device features
The emulators contain a web browser, an MMS client, a Java ME environment, and a TCP/IP stack. These features enable the testing of content and applications as well as data communication features.

Multiple instances and connectivity
Connectivity among multiple instances of the emulators is supported, enabling interoperability testing of applications that use Bluetooth wireless technology, SMS, or MMS. Each emulator instance is  identified and addressed with its own ‘phone number’.

Default device-behaviour override
Standard device settings can be overridden during MIDlet installation. In addition, maximum Java™ Archive (JAR) file size, the security domain, and KVM heap size can be modified.

Versatile diagnostic window
A diagnostic window provides detailed information on data communication traffic. In addition, memory use, browser source, history, and log information are available.

MIDP speed simulation
An emulator’s KVM execution speed depends on the PC hardware, operating system, and mix of applications and background tasks running. With the use of KVM speed controls, the PC execution speed can be decreased to simulate a device’s processing speed.

Configurable MIDP monitoring
The debugging process can be enhanced by controlling information sent to the console or a print file while an application is running in an emulator.

Fast MIDlet testing
The SDK is optimised for repetitive MIDlet testing through a ‘use same instance’ option that resets the Java ME environment, typically in less than three seconds.

Event generator
Events, such as incoming calls, can be generated to test the application’s response to those events.

Keyboard support
Use of a PC keyboard and mouse to interact fully with the emulator is supported.

Canvas window
In addition to the primary, full-view window, the Canvas window provides an enlarged view of the LCD area, allowing for closer pixel inspection, application demonstrations, screen shots, and similar tasks.

Copy LCD to clipboard
The device LCD portion of an emulator can be copied to the PC clipboard for easy inclusion in other applications.

Languages
An emulator’s language can be changed, simplifying the development of localised applications and content. The SDK is shipped with English and other commonly used languages preinstalled.

Command-line interface
A command-line interface allows an emulator to be used with other IDEs or proprietary environments or to be adapted to other specific needs.

Device UI replication
Each Series 40 emulator implements the UI of a specific Series 40 device. As such, the look, key layout, key definitions, error messages, display (1:1 pixel ratio), softkeys, and menu selection allow developers to assess how an application will look and behave on a specific production device and, more broadly, on any Series 40 device based on the same edition and feature pack.

Documentation
A user’s guide, release notes, installation and configuration notes, and Java API documentation are available with each SDK.

Where can I get more information on the contents of the Series 40 platform SDKs?

For more information on specific SDKs earlier than the Series 40 6th Edition SDK, download and read the:

• Series 40 5th Edition SDKs data sheet.
• Series 40 Platform 3rd Edition SDK data sheet.
• Series 40 Platform 2.0 SDK data sheet.

Rate This