Kengkaj Sathianpantarit wrote:About Applets, I don't know why it's not popular, there is nothing wrong with it, except bad marketing, and huge size of JRE.
I've seen many Applets that work very well. And I've seen a commercial Applet that runs on browser and have rich UI long time ago, at that time nobody talks about "AJAX". Applets are so powerful, they are more or less Java applications on web browser.
n Profile is defined as:
The KVM + core library/classes implementation.
additional apis provided to leverage the features of particular category of devices on top of configuration chosen
The memory footprint for MIDP 2.0 along with CLDC implementation is: 0.8 to 1MB
Sun Java Wireless Agent
The piece of software having the mapping of instructions in the from of bytecodes to their corresponding instructions for underlying platfrom+ API implementor+ implementor of other stuff(GC,Thread Management etc.)
The aim is binary compatibility. Each particular host operating system needs its own implementation of the JVM and runtime. These JVMs interpret the byte code semantically the same way, but the actual implementation may be different. More complicated than just the emulation of bytecode is compatible and efficient implementation of the Java core API that has to be mapped to each host operating system
Bert Bates wrote:Hi Guys,
Thanks for the encouragement! We'd really, really like to write an ME book! I just responded in another thread that my guess is the reason ME hasn't taken off is because the phone manufacturers can't seem to agree on any standards, so deploying an app across different phones is such a big pain!
What surprises me is that big companies don't pick a type of phone for their employees, and write apps for that specific phone?