kAWT Version 0.95

kAWT Version 0.95

(c) by Kroll & Haustein GbR 1999-2000
The goal of the kAWT project is to provide a simplified version of AWT for the KVM: The original com.sun.kjava classes included in J2ME CLDC KVM 1.0 differ from the standard Java UI components in many aspects.

See:
          Description

kAWT Packages (Palm specific)
java.awt Contains all of the classes for creating user interfaces and for painting graphics and images.
java.awt.event Provides interfaces and classes for dealing with different types of events fired by AWT components.
java.awt.image Provides classes for creating and modifying images.

 
Additional kAWT Packages (Palm and Desktop)
de.kawt Provides additional AWT-Components that are not part of the standard AWT for the use on the Palm and the Desktop
de.kawt.midp Provides specific classes for kAWT use with SUNs MIDP emulator (EA1)
de.kawt.shell Provides fileshells that are not part of the standard AWT for use on the Palm and the Desktop.

 
Networking Packages (Palm specific)
java.net Provides the classes for implementing networking applications.

 
IO Packages (Palm specific)
java.io Provides for system input and output through data streams, and the file system on top of the File System Emulation.

 
Other Packages
java.util Contains event model.

 

The goal of the kAWT project is to provide a simplified version of AWT for the KVM: The original com.sun.kjava classes included in J2ME CLDC KVM 1.0 differ from the standard Java UI components in many aspects. Thus, porting applications to the PDA becomes a bit complicated. The most important problem is that only limited support for event handling is provided by KVM. Our simplified version of AWT does not let all AWT programs run on the Palm without adoption, but at least the other way around should work: Applications designed for kAWT should run on the "big brothers" of the KJava platform without needing any additional modifications like wrapper classes or similar.

In contrast to the original AWT, the kAWT is implemented all lightweight similar to SWING, so for other platforms than PalmOS only Graphics, Toolkit and a SpotletWrapper need to be ported. The tradeoff is getting the same "Look and Feel" on all platforms since pluggable Look and Feel is not supported in kAWT.

The current kAWT implementation is a "clean room" implementation not depending on original SUN Java code, but of course on the AWT documentation.


kAWT Version 0.95