How is developing for an emulator different from developing for a hardware device?
The emulator supplied with the WTK is a fairly realistic simulation of a MIDP device, down to the telephone-style keypad and display. However, the emulator does run on a real JVM, and may not have the memory constraints of a real hardware device. It may also allow Java operation that would not work at all on a hardware device, such as floating-point arithmetic. One notable omission in the WTK emulator is the ability to simulate the pausing of a MIDlet. When a MIDlet is loaded, it remains in the active state (see below) until it is terminated. As a result, it is difficult to test that your startApp() and pauseApp() methods are properly complementary to each other. The developer should therefore take particular care to code the resource allocation and deallocation strategy properly.
Related Questions
- I own the Palm OS (or other version) of DSSxxxx, and I just changed to a Pocket PC (or other device with a completely different OS). Can I update my program to the other version?
- What are the different methods of deliver for DEVELOPING PROOFREADING AND EDITING SKILLS by Sue Camp?
- Whether WG is a device, hardware or software?
