Java ME MIDP 3.0 in hand


Java ME MIDP 3.0 shipped recently, and the Janitor has already one of the developer phones in his hand as he writes (no jokes about one handed-typing please), complete with battery, clock and Twitter MIDlets and more. No big deal, but its the MIDlet environment that's really changed.

These MIDlets, which can now run concurrently, in the background, can start when the phone boots, can run as the idle screen, and can talk to each other thanks to the new inter-MIDlet communication mechanism, share libraries and respond to a bunch of phone events. And there's a raft of graphically related improvements to jazz up the look, especially on larger screens.
Comments:

These are all great features.

But I'm curious why for example JSR-253 (the MTA APIs) or similar functionality is not included in the MIDP 3.0? Or is it? That way manufacturers would have been forced to include it in their next generation of mobile phones.

It feels a little bit strange to run an application on a mobile phone, and not to be able to make a call with attaching a listener to respond to the outcome of that phone call for example. Using 'platformRequest' to place a call is not an alternative at all, and is poor approach for a platform as robust as Java. There are some other useful functionality defined in JSR-253 and judging by the forum posts a lot of developers would not just welcome it but need it. Without it, we are forced to look for workarounds, that just hurts the portability of the applications.

Posted by Lazo Lazarev on January 13, 2010 at 06:13 PM PST #

Post a Comment:
Comments are closed for this entry.
About

A blog all about Java in all its flavors on all client platforms from smartcards to desktops and everything inbetween.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
Feeds