Also, the feature set includes support for features not found on handheld devices. While the AWT has a rich feature set, it is mainly desktop-based.The component set of the AWT is designed to work with a pointing device such as a mouse however many handheld devices, such as cell phones, have only a keypad for user input. The AWT assumes certain user interaction models.The AWT is designed for desktop computers and optimized for these devices.The MIDP Expert Group decided not to subset the existing AWT and Project Swing classes for the following reasons: This article concludes with guidelines to GUI programming for mobile information devices.
#ABSTRACT WINDOWS TOOLKIT HOW TO#
That discussion is followed by a description of the GUI classes included in the MIDP with examples of how to use them. Because the MIDP GUI classes are not based on the AWT, this article starts with a brief discussion of why the MIDP Expert Group made that decision. This article discusses the details of GUI programming for handheld devices.
The GUI classes included in the MIDP are not based on the Abstract Window Toolkit (AWT). Official GUI classes for the Java 2 Micro Edition (J2ME) are defined by the Java Community Process (JCP) and are included in profiles such as the Mobile Information Device Profile (MIDP). For example, the CLDC itself does not define any Graphical User Interface (GUI) functionality. The CLDC provides foundation classes for all resource-constrained Java-enabled handheld devices and needs to be complemented by profiles. For these reasons, you cannot follow the same user interface programming guidelines for applications running on desktop computers and hand-held devices. For example, the display size of handheld devices is smaller, and the input devices do not always include pointing devices, for example, a mouse or pen input). The user interface requirements for handheld devices are different from those for desktop computers.
0 kommentar(er)
