Tutorial Home | Next

JSR 271 defines MIDP3.0. MIDP Expert group is still working on this version and some of the specifications may change in the final release. Overall MIDP 3.0 platform seems to be going the desktop way. It adds lots of desktop functionality and the analogues with desktop and server jargon is given below

• CDC stack in addition to CLDC stack. CDC is slightly similar to JDK
• LIBlet’s which are libraries like DLL’s and Shared Objects in desktop environment.
• MIDlet concurrency which is analogues to multiple processes running at the same instance like in the Windows applications. May be some of the device vendors give us a tab key on the keyboard.
• IMC(Inter MIDlet Communication) which is analogues to (IPC) Inter Process Communication in the desktop and server applications
• RMS Interchange file format is analogues with database create/delete scripts or database import/export mechanism.
• Screen Saver and Auto Start MIDlets are analogous to desktop screen savers and application auto start when the computer is switched on.

MIDP 3.0 seems to open up some exciting avenues for application developers. This release seems to address most of the features which the developers have been asking for.

This tutorial is a first draft of a new series of tutorials on MIDP3.0 by j2meSalsa and will grow as things become concrete. New classes and interfaces added to MIDP 3.0 are listed below. Detailed description these classes are in their respective sections in this tutorial.

• AnimatedImage
• AutoStartPermission
• FileSelector
• DisplayCapabilityException
• DisplayListener
• EventData
• EventDataListener
• EventManager
• EventPermission
• FileSelector
• FontFormatException
• FormLayoutPolicy
• IdleItem
• IMCConnection
• IMCServerConnection
• ItemLayoutHint
• ItemLayoutInfo
• ItemTraversalListener
• Manager
• Menu
• MIDletIdentity
• Notification
• NotificationException
• NotificationListener
• NotificationManager
• PushRegistryPermission
• TabbedPane
• TableLayoutPolicy
• TabListener
• Text
• TextInput
  
• TextInputListener
  
• UserAllowedPermission
  

MIDP3.0, CLDC and CDC

In earlier versions of MIDP was sitting on CLDC(Connected Limited Device Configuration) only. Now with MIDP 3.0 sits on CLDC and/or CDC(Connected Device Configuration). This change in architecture does not make any difference to the MIDP application developers but has some implications if you a KVM developer. CLDC is designed for devices with 128 KB to 512 KB RAM and CDC is designed for 2MB of RAM. This means that the MIDP engines running with CDC will have larger memory footprint. To cut the whole story short “MIDP applications running with CDC stack will give you better performance”

Tutorial Home | Next

More Tutorials

MIDP for Beginners
MIDP Gaming
JSR 179: Location Based Services

This page is a part of a frames based web site. If you have landed on this page from a search engine click here to view the complete page.