Technical sessions | track five | java me – Google 2007 JavaOne Advance Conference Guide User Manual

Page 40

| technical sessions | track five : java ME

| java.sun.com/javaone

* Content subject to change.

TECHNICAL SESSIoNS

| TRACK FIVE | JAVA ME

Java ME

TS-5743 Graphical, Scripted, and Animated user Interfaces on

Java ME

Vincent Hardy, Sun Microsystems, Inc.
Nandini Ramani, Sun Microsystems, Inc.

This session discusses various technologies and techniques that enable
developers to create highly graphical, animated, and scripted user
interfaces on Java ME.

The session focuses on showing code samples articulating how to create
such user interfaces and explains which APIs can be used today, such
as the Scalable 2D Vector Graphics API v1.0 (JSR 226), as well as what is
becoming possible with new and upcoming APIs such as the Scalable
2D Vector Graphics API v2.0 (JSR 287) and the Java Language & XML User
Interface Markup Integration APIs (JSR 290).

On the Java ME platform, it has long been difficult or simply not possible
to create graphics that adapt to the display resolution and the display’s
aspect ratio. Likewise, there was no simple way to create, generate, and
run animations to manipulate user interface elements. Additionally, the
set of user interface components available on MIDP was fairly limited.

With the new APIs already available (JSR 226) or coming to the Java
ME platform (JSR 287, 290), these limitations are lifted and developers
can import, create, and play animations; trigger them when needed
by their application; scale their graphics to the display’s resolution;
render them to the desired aspect ratio; and create reusable user
interface components. The goal of this session is to illustrate how to
implement these features, with demonstrations of shipping devices as
well as code examples.

TS-5906 Building a Java ME Test Suite in 15 Minutes

Alexander Glasman, Sun Microsystems, Inc.
Mikhail Gorshenev, Sun Microsystems, Inc.
Roman Zelov, Sun Microsystems, Inc.

JT Harness and Java ME Framework are the open source tools developed
on java.net (jtharness.dev.java.net, cqme.dev.java.net/framework.html).
JT Harness is an open source version of Sun’s JavaTest harness, which has
its origins in the beginning of Java technology: its first version was used
for the testing of the JDK 1.0 release. In the 10+ years that followed, it
evolved into a mature, full-featured test harness. Java ME Framework is
a Java ME plug-in for JT Harness that provides support for the different
flavors of Java ME.

This session is targeted at Java ME developers and quality engineers who
need automated unit or regression testing. It addresses device limitations
such as memory size and processor speed typical for Java ME phones and
dealing with VM crashes and resource leaks. Also it discusses how to
overcome test suite scalability problems and shows how large, stable test
suites are put together.

A demonstration shows how to use JT Harness and Java ME Framework to
create a simple Java ME test suite and run it on a Java ME device.

TS-5913 Tools for developing Advanced Mobile Multimedia

Applications

Jay Indurkar, Sprint Nextel

JSR 135, Mobile Media API, is a very powerful API that enables developers
to create innovative applications, as demonstrated by some of the
applications that run on Sprint devices (Sprint Music Store, the first
music full-track wireless download service launched in the U.S.; Mobi TV,
the first application that allowed developers to watch live streaming TV).
JSR 135 is one of the APIs that elicit a lot of questions from developers;
a “Best Practices in Utilizing JSR 135” would help educate developers
currently using Java ME and entice other developers to explore some of
its capabilities.

This presentation covers the following:

• An overview of JSR 135 (play media files, take pictures, and so on)
• An existing multimedia application that highlights the capabilities of

the JSR (stream RTSP file, play media clip file, take pictures, and so on)

• How to build a sample application utilizing NetBeans software

customized for Sprint (Sprint Mobility IDE with multimedia components
to initialize the player, access files from external memory, and so on)

• Tips/best practices/errors most common in utilizing JSR 135 (incorrect

permission declarations, incorrect player initialization, handling
background threading with the foreground UI operating)

• Compiling and running the project in the emulator
• Deploying the application onto an actual Sprint handset that replicates

the features shown at the beginning of the session

At the end of the session, the attendees should have a good
understanding of the capabilities of JSR 135, best practices/tips and
tricks they can incorporate into their own application, and how to
develop an application that utilizes JSR 135 and deploy it to run on a JSR
135-enabled handset.