Your SlideShare is downloading. ×
03 midp
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

03 midp

530

Published on

J2ME MIDP

J2ME MIDP

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
530
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
28
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Mobile Information Device Profile Cornelius Koo - 2005
  • 2. Hardware Requirements• Screen dimension at least 96x54 pixels• At least one type of user input available, eg. one handed keyboard• 128 kb non-volatile memory to run Mobile Information Device (MID) components• At least 8 kb of non-volatile memory for applications to store persistent data• 32 kb of volatile memory to run Java• Wireless network connectivity
  • 3. Software Requirements• OS running on device must provide minimal scheduling, exception handling and processing of interrupts.• Able to run JVM• Must support writing of bitmapped graphics to the display• The software must accept input and pass the information to the JVM• able to read and write to/from non-volatile memory
  • 4. MIDP ArchitectureOEM = Original Equipment Manufacturer
  • 5. MIDlet & MIDlet Suite• MIDlet : Java App. Designed to be run on mobile application• MIDlet Suite : Consists of on or more MIDlet packaged on .jar file
  • 6. Application Manager• Software on a mobile device that is responsible for installing, running and removing MIDlets• This software is device-dependent
  • 7. Application Manager• When Application Manager runs it will make these available :• Access to CLDC & JVM• Access to MIDP defined class• Access to JAR file• Access to Java Application Descriptor File
  • 8. MIDlet Java Archive (JAR)
  • 9. Six Must-Exist Entry• MIDlet-Name• MIDlet-Version• MIDlet-Vendor• MIDlet-<n>• MicroEdition-Profile• MicroEdition-ConfigurationMust exist in the Manifest file
  • 10. JAR MIDlet Attributes
  • 11. ExampleManifest-Version: 1.0MicroEdition-Configuration: CLDC-1.0MIDlet-Name: Basic Midlets Midlet SuiteMIDlet-Vendor: Midlet Suite VendorMIDlet-1: HelloWorld,,HelloWorldMIDlet-2: HelloWorld,,HelloWorldMIDlet-3: HelloWorld2,,HelloWorld2MIDlet-Version: 1.0.1MicroEdition-Profile: MIDP-2.0
  • 12. Java Application Descriptor (JAD)
  • 13. Why JAD ?• Provide the application manager with information about the contents of a JAR, so that it can decide whether a MIDlet suitable to run on the device or not.• Provide a means for parameters to be passed to a MIDlet without changing the JAR file.
  • 14. Must-Exist Entry• MIDlet-Name• MIDlet-Version• MIDlet-Vendor• MIDlet-<n>• MIDlet-Jar-URL• MIDlet-Jar-Size
  • 15. JAD MIDlet Attributes
  • 16. ExampleMIDlet-Jar-Size: 1783MIDlet-1: HelloWorld,,HelloWorldMIDlet-2: HelloWorld,,HelloWorldMIDlet-3: HelloWorld2,,HelloWorld2MIDlet-Jar-URL: Basic_Midlets.jarMicroEdition-Configuration: CLDC-1.0MIDlet-Version: 1.0.1MIDlet-Name: Basic Midlets Midlet SuiteMIDlet-Vendor: Midlet Suite VendorMicroEdition-Profile: MIDP-2.0
  • 17. Reference• Core J2ME Technology and MIDP. John W. Muchow. Prentice Hall PTR, 2002.

×