Technical Documentation
Main differences between AWT and kAWT
The main differenced between AWT and kAWT are:
- kAWT supports only one event listener of each type per Component. If more listeners are really needed for a certain application, a simple dispatcher can be used as workaround.
- Like Swing, most kAWTcalls are not thread-safe. In order to allow kAWT-usage in multi-threaded applications, since version 0.95 kAWT allows thread-safe event-queue-entries, similar to the Swing "invoke later" mechanism and fully compatible to AWT. Use java.awt.EvenQueue to access this mechanism.
- Similar to Swing, all kAWT components are lightweight component written in pure Java, leading to simpler code portability.
Roadmap
The following table shows our future development plans for kAWT:
Version |
kAWT (Palm) |
RMS Emulation (Palm) |
File Emulation (optional) |
RIM Port |
MIDP Port |
1.0 |
stable |
test version |
test version (palm only) |
test version |
test version |
1.5 |
stable |
stable |
based on RMS |
? |
? |
2.0 |
stable |
stable |
stable |
stable |
stable |
3.0 |
PDAP compliant |
PDAP compliant |
stable |
PDAP compliant |
PDAP compliant |