Overview

Project Capuchin assists developers in three ways:

1. Make Flash applications much more capable by using Java code for logic and API access to the phone
2. Enrich Java applications by providing a more sophisticated user interface in Flash
3. Package a pure Flash application as jad/jar, enabling it to be uploaded and sold as an application on PlayNow. The SWF2JAR tool makes this really simple.

Project Capuchin enables faster UI development and easier collaboration between graphical designers and code developers.

Once all interfaces between the presentation and service layers have been defined, UI designers can develop and test the presentation layer in the Flash environment independent of the Java development and testing of the service layer.

Project Capuchin was introduced in 2008 with Sony Ericsson Java Platform JP-8.4. Sony Ericsson’s phones based on Symbian and Windows Mobile also support Project Capuchin.

• See phones supporting Project Capuchin the Phone Gallery>>

Project Capuchin Model

The Project Capuchin API defines several different classes that can be used for developing Java MIDlets, for example, classes to communicate directly with the native Flash player in the phone, classes to play Flash content in a Java Canvas object, and classes for data transfer.

The Flash file (.swf) is included in the MIDlet jar and is started from the Java MIDlet via a call to the Project Capuchin API which invokes the Flash content.

Data transfer interfaces and corresponding classes and function calls should be defined before starting development of the actual Flash and Java applications.

There are two types of data transmission methods:

• Data requests where the MIDlet handles a request of data from the Flash application, and returns data asynchronously. To handle the request, the MIDlet may use any of the JSRs available on the Java Platform in the phone.
• Flash content receives events triggered by the MIDlet.