I know you think that Java and Web Runtime does not have any built-in interoperability today, and this is almost true. So what is the catch? How can you create a widget that uses java APIs?

Starting with the S60 Feature Pack 2, java runtime introduced the new UI toolkit for Java, namely eSWT. eSWT includes an amazing component called Browser. Browser is one of the ~40 components of eSWT and its purpose is to provide access to the platform's native web browser. In our case, this is the S60 Browser Control. Using eSWT's Browser you can embed a browser into your Midlet. The end result is a Midlet that hosts S60's WebKit based Browser. Although it is not the purpose you can actually create your personal Browser with it, there is is a simple example on Forum Nokia wiki demonstrating this.

So what is the web runtime connection? Just like eSWT's Browser, the heart and soul of Web Runtime is S60 Browser. When eSWT initializes its Browser component, eSWT pretty much enables similar functionality to Web Runtime. As a result, all the AJAX programming available with Web Runtime is available but this time embedded inside a Midlet. Of course being embedded into a Midlet has advantages. Your web widget can now access all the local resources, use APIs like location and PIM and generate the content with the help of these Java APIs and set it to the Browser. It is even possible to mash up the local data with the online services, (Google Maps, Flickr etc.)

There is a little known program run by S60 Java platform team. We regularly work with software and game houses to find out about the problems on our platform and also help them solve problems on their applications. We hope to extend our reach with this BOF to broader developer community. I will be at the BOF and will be sharing some usability tips, I know that most of the S60 engineers that are attending the conference are going to be there. I am really hoping to hear about some of the performance tips and also problems that you face when working with the S60 Java platform.

This year, we will have several of the engineers and architects that build the java platform for S60 available during the conference. We will be occasionally hanging around the Nokia booth on the Pavillion. If you have questions or opinions you want to share or just like to see a demo and some code, find the Nokia booth on the Pavillion. If you want to meet S60 java bloggers,  Aleksi and I have scheduled ourselves to be at the booth on Tuesday after 16:00, during the JavaOne Pavilion Welcome Reception. We will be very happy to meet you.

In case you have not heard of WidSets, I recommend you to take a moment and visit WidSets website. In a nustshell, WidSets is a widget platform. Simply put widgets is the name of the general concept of small applications that runs on devices and PCs. Widgets are commonly used to show web content, such as news, blog feeds etc.

One of the features of WidSets that amazes the little engineer in me is WidSets provides a user interface and scripting language itself. In a sense, it is a full-blown platform that runs on top of the java platform. The scripting language is good enough to allow developers to develop small applications, such as sudoku or chat for the platform.

But my vote for best WidSets feature is content discovery. If you are looking for some content to use in your mobile phone, it is probable that WidSets have it. WidSets web site and mobile client provides several ways to explore the available content. The list for the existing content is comprehensive and growing. If you happen to be a content provider then WidSets is an easy way to share that on mobile world and it is amazingly effective. A few days ago, I have experimented with WidSets to create a widget that shows the content of my personal blog and I was surprised to find that I had around 20 users in less than 24 hours.

Overall, WidSets is a highly recommended java application if you are looking for ways to consume web 2.0 content on your S60 phone.

The article was originally published in S60 News magazine. S60 News is a newsletter for S60 licensees, S60 Product Creation Community Members and Operators. Since eSWT is a new public Java API for rich user interface creation I thought it's best to make the article available to anyone. Here you go:

"Taking S60 Java Platform user interface capabilities to the next level"
Download PDF file

Note: Streaming of video uses a lot of data so watch out if you don't have a flat-rate, unlimited data plan!

The embedded video is streamed with S60's Real Player and you have to configure the access point settings also to it: http://www.google.com/support/youtube/bin/answer.py?answer=87023&topic=13744.

We have Javadocs for the new APIs: eSWT and IAPInfo. You can also find API overviews and examples for these from UI and graphics and Networking sections, respectively. We've put back the Nokia UI API Javadoc as it's still used by applications and since the standard MIDP 2 API doesn't have all the functionality; we'll try to aim this with MIDP 3 standard in future.

The library also has significant update on MIDP implementation notes document. There we have a table of Nokia specific JAD and JAR attributes for easy reference. There's also Scaling topic about Canvas graphics scaling and scalable MIDlet icons, and a System properties table.

The primary reason for us doing open source is to improve the compatibility of our API implementation. Opening implementation code for an API will also allow other parties more easily start implementation of the same API on other platforms. Since the implementation mostly shares exactly as-is much of the code base this improves directly compatibility more than just some technology compatibility kit (a test set verifying API signature and expected API behavior). Testing never grabs all the details, similar API compatibility tests won't test everything. Sharing implementation code will ensure in a much better and simple way behavioral compatibility. Open source is thus a way to truly limit fragmentation - a too much used curse word among java apis.

However, the open source license has to be such that it allows commercial usage of the code. The API implementation code must be possible to be used as part of closed or proprietary products. Also the license must not have a viral effect on applications using the API. Open source API implementation should not mean that the applications using that API are also forced to be open source. In other words linking from code with a different license should be allowed. I personally for example would like to see much more mobile Java APIs being developed in open source style licenses.

Open source way of working is also lot more fun. You get to be more in contact with potential clients for your API as well as discussions with other implementation teams is more easy as communication can be open.

M2G allows to render SVG content inside Java applications, and it's already available in latest S60 and Series 40 devices out there (Nokia N95 etc.). It basically allows very easy way for reaching 2D graphics scalability. Making device resolution independent games has been hard this far and many games are simply fixed to certain resolution only. Game publishers had to do multiple variants for the same game for multiple resolutions. I'm eagerly waiting for some games to utilize this. Of course it's not just games the technology is targeted, you can use it also to create fancy looking 2D UIs.

But there's a lot more in the new S60 Java Platform. We have both, new API features and under-the-hood functionality. Below I'll try to list most of the nitty-gritty features. We'll be providing more information on how to use these via Forum Nokia Wiki site, and perhaps cover some in more details in future posts here too. They will also be covered in our reference documentation in Java ME Developer's Library when a 3rd Ed FP 2 version will be available.

New APIs available:

• Nokia IAPInfo API
  
• Device dedicated Media keys (Play/Pause/Stop) access as normal key events
  
• Control over End call key (Red call key) behavior for application's lifecycle
  
• Enabling device theme background for Canvases for custom component usage
  
• Prevention of screen saver via Nokia UI API
  
• Foreground/background events via pauseApp/startApp
  
• Flip close event for fold/clamshell devices via pauseApp
  
• Access to device IMEI, network access type (gprs / csd etc.), network id, network signal level, battery level, country code, date and time formats via system properties
  
• LCDUI Canvas Graphics scaling (introduced originally in 3rd ed) enhanced for orientation switching devices
  

IAPInfo API allows to access device's Internet Access Points configuration and allows to specific explicitly for General Connection Framework network connections (http etc.) which IAP should be used.

New other functionality:

• Java application startup time is better due to OS on-demand paging and other changes (and as a result you also have more user RAM available).
  
• Support for scalable icons (SVG) for MIDlets
  
• Support for categorization of MIDlets: game / application
  
• Device volume keys will change audio output volume of MMAPI
  
• Selection key has a label (as a result LCDUI Commands are more aligned with Series 40 Java)
  

New architecture

Regarding under-the-hood functionality, the S60 Java Platform has gone through a big architectural change. We've changed the VM from a monolithic architecture to more flexible one. Prior to 3rd Ed fp 2, S60 Java had traditional CLDC VM architecture where all API code (class files) were compiled into the virtual machine executable. Now the Java API implementation code is no longer in the VM executable but will be dynamically loaded when needed.

The new architecture allows us to dynamically extend the virtual machine with new APIs. Which is exactly what is used e.g. in our eSWT implementation. When there will be new releases available from us for eSWT, we'll release that directly to developers. Anyone can install that upgrade package to 3rd ed FP 2 devices. Another result of the new architecture is of course memory saving: applications not needing some of the optional APIs wont have them in memory.

We also have changed the threading implementation. Now Java Threads are native. Each Java Thread has a native thread counterpart. Prior to 3rd FP2 the Java threads used so called light-weight threading (sometimes referred to as "green threads" which is a small misnomer) where Java VM had it's own thread implementation and scheduling. Now Java threads are scheduled by OS.

Runtime performance

On MMAPI we have done performance improvements. In overall the mixing of audio content now works lot better and playback latency is smaller. This means improvements to Java gaming experience. The media deallocation now properly frees the memory and concurrent number of players being in pre-fetch state is increased.

One smaller, but rather dramatic change has been implemented on LCDUI Canvas class. Previously each Canvas instance contained it's own double buffer for graphics contents. The size of the buffer image is the size of the screen so it consumes quite much runtime memory. Double buffering for Canvas is nowadays required feature by MIDP specification 2.1. If a MIDlet has multiple Canvas instances the memory may easily run out. On other platforms e.g. Nokia Series 40 had implemented different double buffering scheme: each Canvas instance simply shared the same double buffer. We at S60 Java decided to implement the same scheme and as a result we are behaving the same with Series 40 devices.

On S60 devices users may access Java application specific settings via Application Installer menu item. In the list showing installed applications there's an options menu item "Suite settings" (on 3rd ed FP 1 it's just "Open" menu item).

On 3rd ed FP 1 devices you will be able to configure a default Internet Access Point for that particular Java application. If you set it the application won't never prompt you for the access point but automatically uses the specified IAP when connecting to network.

The device access settings are also configurable via the same view but mostly this only makes sense for signed applications as the available settings for unsigned (aka unidentified) 3rd party applications are forced to be more prompting as defined by Java specifications (MIDP, JTWI and MSA security recommendations).

We are also working on improving this functionality even more on S60 3rd ed fp 2 devices (read: getting rid of those annoying prompts). But more out of that later when details are more solid.

Btw: The Internet Access Point prompts are S60 specific feature which isn't available in other platforms, at least to my knowledge. Many other Java devices simply use the same access point as configured for Browser. S60 is more flexible as you can use a specific access point for each Java application. For example, Browser may be configured to operator's "WAP access point" and a certain Java application to more free "Internet" access point.

I am working as part of the organization that develops the Java platform for S60. Like most of the Java platform team, I am based in Tampere, which is located in Finland. On my daily work, I work with a group of talented people to create advanced stuff for the Java platform. Some of our publicly available work is eSWT UI toolkit for S60, which we had a posting about in this blog sometime ago and also the open source eRCP runtime. I also run a second blog that has more regular postings about eSWT and eRCP. Hmm... what else, I am a dog person, meaning I have a dog. I have joined Nokia because it would give me access to the cool devices and now it is addictive. And my star sign is Leo.

The graphics capabilities of Java are already very rich but so far, the capability of the S60 Java platform UI toolkit (MIDP LCDUI) has not been on par with the S60 native UI frameworks. However, the S60 3rd Edition FP 2 changes this dramatically by introducing a completely new UI component toolkit to the Java Platform called eSWT. Standing for embedded Standard Widget Toolkit, eSWT is a significant facelift for Java UI frameworks.

eSWT is a cross platform toolkit developed in cooperation in Eclipse open source project called eRCP. What's even more interesting is that eSWT shares most of the API with desktop SWT.

The eSWT API provides:
- A rich user interface component set
- Flexible and scalable layout system via layout managers
- Rich user interface events
- Access to native UI functionality on par with smartphone UI frameworks.

Screenshots from an example application using eSWT

Since eSWT on the S60 has been implemented using the normal S60 UI services, applications built using it will automatically have the standard look and feel of S60, including S60 themes and internationalization features.

The eSWT plugin for S60 Java SDK is available:
eSWT plug-in for S60 3rd Edition SDK for Symbian OS, Supporting Feature Pack 2, for MIDP, Beta.
You need to have the beta SDK which is available here:
Java SDK for 3rd Edition, FP 2, Beta.

The plugin implementation for the SDK is identical to the actual device implementation. It is just compiled to S60 emulator target (Intel). We are very interested to hear your comments about the new toolkit.

There's different ways to contact us. We are part of the Eclipse eRCP project so you can post comments to the Eclipse eRCP newsgroup. On how to access see eRCP project pages for info. For bugs you may find a report to Eclipse Bugzilla is preferred. Or you can drop a comment also to this blog.