| ID | CS000958 | Creation date | May 14, 2008 |
| Platform | S60 3rd Edition, FP1 | Tested on devices | Nokia N95 8GB |
| Category | Java ME | Subcategory | Files/Data |
| Keywords (APIs, classes, methods, functions): |
This code snippet demonstrates how to add an icon to a MIDlet.
The manifest file provides information about the MIDlet. To add an icon to the MIDlet, add MIDlet-<n> attribute to the manifest file, where n is an integer identifying the MIDlet:
MIDlet-1: midletName,icon,mainClass
Here is a complete sample manifest:
MIDlet-Name: MIDgetSuite
MIDlet-Vendor: Vendor, Inc.
MIDlet-Version: 0.1.0
MicroEdition-Configuration: CLDC-1.1
MicroEdition-Profile: MIDP-2.0
MIDlet-1: MIDget,/icons/icon.png,MainEngine
It is also possible to add information about the MIDlet into a so-called Java application descriptor file (JAD). JADs are useful because instead of downloading the whole – possibly large – JAR file, a MIDP device may first fetch the application's JAD file to provide the user information based on which he or she can decide whether the MIDlet is worth downloading. The JAD file is not required, and it does not directly relate to icons (most of the S60 devices ignore the icon definition), but here is an example of it:
MIDlet-Name: MIDgetSuite
MIDlet-Vendor: Vendor, Inc.
MIDlet-Version: 0.1.0
MicroEdition-Configuration: CLDC-1.1
MicroEdition-Profile: MIDP-2.0
MIDlet-Jar-Size: 2245
MIDlet-Jar-URL: MIDgetSuite.jar
MIDlet-1: MIDget,/icons/icon.png,MainEngine
Note: According to KIJ000524 - MIDlet attributes on JAD and manifest files have to match, the attributes common to both the manifest file and the JAD file must be identical.
After the MIDlet is packaged into a JAR file and installed into a device, the specified icon is shown.
No related wiki articles found