The Series 40 full touch platform introduces for the first time the Series 40 device with a full touch display. These devices do not have a physical keyboard, and have only call creation and call termination keys as the mandatory physical keys. Text input on these devices can be done using a virtual keyboard displayed on the touch display.
The aim of this section is to outline what has changed in this platform with regard to touch input, and how to modify your existing MIDlets to work and take advantage of the Series 40 full touch UI.
Feature |
Non-touch |
Touch and type |
Full touch |
|---|---|---|---|
Display Resolution |
128 x 160 240 x 320 320 x 240 320 x 480 |
240 x 320 pixels Aspect ratio is 3:4 |
240x400 pixels Aspect ratio is 3:5 |
Keyboard |
Physical keypad Physical softkeys Navigation Keys |
Physical keypad Virtual softkeys |
Virtual Keyboard Physical Keys for call creation and termination |
Command mapping |
Mapped to physical softkeys |
Mapped to virtual softkeys |
Mapped to action buttons |
Before you begin, refer below topics to get a better understanding:
You can make your existing MIDlets functional in full touch platform by doing the following minimum changes. For both high-level and low-level UIs, the common step involved is:
The additional basic steps for low-level UI based MIDlets are:
You can enhance the usability of your existing MIDlets in full touch platform by adding the new features:
There are more new features in Java Runtime 2.0.0 which you can make use of in your MIDlets. For the complete list, see New features in Java Runtime 2.0.0 (full touch devices).
You can find example MIDlets ported from touch and type to full touch here: