Following my last post, I’m analyzing the Future of Java ME (J2ME).

Designing new UI with SVG

Standard Vector Graphics format, will be one of the revolutions in Java UI designs, using an SVG subset called Tiny SVG. Everyone who developed a Graphic User Interface using LCDUI Canvas (or FullCanvas in Nokia UI) knows how difficult is to design a cool UI interface; we have to do everything with Java code with a few shape methods (like fillRect), or loading heavies PNGs.

Many vendors, all of them in JCP (Java Community Process) are supporting the SVG API (JSR 226). Many SDKs and emulators are supporting it, and Nokia’s devices are supporting it from Series 40 3rd edition Feature Pack 1 and Series 60 3rd edition Feature Pack 1. You can find a great document from Forum Nokia about this API here

SVG has many advantages, as the following ones:

• It’s a standard.
• It’s XML based, so it is a text file, easy to store and transmit.
• It allows to design vector graphics that scales automatically to fit the canvas size of the device.
• It allows vector animations.
• It allows to define hotspots over the image, to be navigated and selected by the user (yes, we can “listen” to this events).

So, from Java code we can capture when a user selects a hotspot, and we can also animate and modify the SVG elements structure dynamically. For example, we can change an object property (color, size, rotation, etc.), we can add new elements (like shapes, other SVG document) when we need it.

Using this technology, not only we are having greats advantages over using Canvas and Graphic classes, we can integrate graphic designers in our team easily. SVG is a format that every graphic designer can export from a vector tool (like Corel Draw or Adobe Illustrator), so we won’t need to convert designs into PNGs and Java code anymore.

And JCP team is working on a newer API that will extends this one: JSR 287 (SVG API 2.0). This API will work with SVG 1.2 format, that supports multimedia, audio and video, alpha transparency and gradients objects.

Other format waiting in Java ME community is CDF (Compound Document Format, JSR 290). But this is for other post...

Internationalization

For everyone who develops applications for a non-English market (as me), the ability to generate multiple versions for each language is a great feature. JCP (leader by Nokia in this case) worked in the Mobile Internationalization API (JSR-238). Using this API installed in the device, we can handle external resources files per language, and we can format dates, numbers and currency depending on the culture of the user’s country.

This API is currently supported in many IDEs for working in design mode. A great feature of some IDEs is the ability to generate many JAR packages, one per language or group of them.

Contactless

Contactless Communication API (JSR-257) allows mobile devices to read information available around in the environment, using many technologies, like visual tags (bar codes or similars), or RFID (Radio Frequency Identification). This will allow mobile phones to read URLs, number phones, semantic information, prices or other information from the “real world” to the Java ME application.

What’s next

In next posts I’ll talk about MIDP with CDC, Next Generation Mobile Platform, MIDP 3.0 and new tools and IDEs. 

See you on next post!