I think Sun should take the Espial Group approach ( www.espial-group.com ).
Lightweight Java UI can be portable on smaller devices. With specific
'pda.pilot' type packages, you should probably just use a Java to native
compiler (like Jump or a Palm port of TowerJ) with libraries that provide
access to all OS functionality. J2ME applications written specifically to
the PalmOS using the pda.XXX scheme would not be portable, so you would be
giving up performance _and_ portability. I'd also like to point out that
without JNI (reduced portability) no Java implementation has call-for-call
access to any platform's libraries.
As of now, there is not a way for anyone other than Sun to produce the
native call connections for the KVM, because true JNI was considered too
heavy (for now). I'd also like to see what the addition of network code does
to the KVM and Java2ME footprint.
The idea of J2ME is interesting, but unless it can be made source and binary
portable across smaller target devices, the KVM should be replaced by a
compiler. There is no benefit to interpreted byte code that can run on
exactly one platform. I would enjoy writing PalmOS applications in Java. I
just don't want to give up performance without gaining portability.
I should mention Waba here. Waba is portable across PalmOS, WindowsCE and
standard JavaVMs. It doesn't provide access to the entire PalmOS, but you
can get at quite a bit.
TJMOICBW,
Dan
-----Original Message-----
From: Aaron Ardiri <[EMAIL PROTECTED]>
To: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]>
Date: Thursday, July 08, 1999 1:41 PM
Subject: RE: Is the J2ME API suitable for the Pilot?
the KVM is fine.. that can be common.. but the libraries should
have ALL the features of the OS (as you can get in C).
ie:
maybe: pda.common // common objects
pda.pilot // palm pilot specific
pda.wince // winCE specific
for now.. if they are marketing on Palm devices.. they should
support palm (the whole point at JavaOne was the announcement
of J2ME using Pilot as the "hardware" for implementation).
