G1. Do you think it's OK to integrate SuperWaba in this CVS tree ?
G2. Do you think SuperWaba should replace the standard classes and
become part of the standard Waba platform (vs being an option,
like currently) ?
G3. Should Waba on SourceForge (this project) become the central point
- Waba VM
- Waba core packages
- Waba non-core packages
- Waba applications and applets
- other: no answer
Do you intend to contribute to the VM (=core) development:
- for the Palm port ?
- for the Win32/PocketPC port ?
- for the Linux/uClinux port ?
G5. Do you intend to contribute to the development of additional
(=non-core) java packages for Waba ?
- Do such packages require development of native methods ?
G6. Which GUI model do you (intend to) use ?
- Waba / color Waba
- AWT if available
- MIDP (object model for mobile phones) if available
G7. Are you interested in other usages of the VM than applications,
- real applets
T1. Should we have only one object model for both Black+White and
color widgets (i.e. the classes detect the platform's capability
and do the rendering accordingly) ?
T2. Compatibility issues due to the specificities of the different
- The PalmOS has blocking IOs, which makes the lack of threads
particularly annoying (yet solvable with timer). Should the
Palm port simulate non-blocking IOs in the VM, if technically
- Should the Catalog classes be provided for all ports to insure portability ?
- Should the filesystem be simulated on Palm ?
T3. Should the JAR format be supported (at least for non-Palm
- All clones and modifications should be merged into the project, IMHO.
- I would most heartily recommend that the waba.xx original package be
preserved and everything else, (eq super-waba, or waba jump) be done
via sub-packages (eg waba.super.fx, etc)
- I'd like to have a CommonWaba specification, combining the best of
SuperWaba, ColorWaba and WabaCE, but in a portable fashion. E.g. to
the application programmer, it shouldn't matter what platform the
program runs upon, a portable call to create a button should give a
button with a look-and-feel consistent with the rest of the program
and with the platform's defaults.