Typically, you create a MIDlet with an IDE, such as Eclipse or Sun NetBeans, and run it on the SDK.
You can run the MIDlet on the SDK with direct loading. It has the following benefits:
Provides a faster, less restrictive environment in which to test and debug MIDlets during the early phases of development
Lets you develop a MIDlet from within an IDE during which you edit and compile code and immediately display the results on the SDK.
Is a good way to test how a user runs a MIDlet that is already loaded on a device.
The following table provides the details of running a MIDlet on the SDK with direct loading:
|
MIDlet trait |
Direct loading |
|
MIDlet installed in the SDK instance’s Applications folder |
No |
|
Maximum size of JAD file |
10240 bytes (10KB) |
|
Maximum size of JAR file |
2MB (maximum value) 2MB (default value) Value can be changed in Tools>Preferences>MIDP |
|
Maximum MIDlet data size |
1MB |
For more information, see: