> This is what will also happen with CLDC and MIDP, the environment that Sun
> has designed for mobile appliances like cell phones.
>
> It is unlikely that existing Java applications will be run on portable
> devices of PDA size w/o partial re-implementation, in particular if they
> were initially designed for desktop PC screens; they're also quite big (app
> classes + foundation classes) and cpu hungry, and often use swing.

This is true, regarding screen size stuff.  However, your point re: not 
wanting to bring in a new GUI implementation are on point.  You can use kawt 
(www.kawt.de) to bring AWT to CLDC BTW.  Though it's written in a swing like 
way with everything being done lightweight.

> The kind of Java code that one can reasonably want to run on a PDA are
> small applets.
>
> WABA is an alternative JVM for very small devices, comparable to J2ME. But
> unlike J2ME, it is royalties free. Note that the GUI model of J2ME (e.g.
> KVM on Palm) is also specific and quite limited.
>
> We think a stripped-down version of AWT could be a senseful solution, so as
> not to introduce yet another object model. Currently there are the
> following GUI models (at least): - AWT for applets and apps
> - CLDC/MIDP for cell-phones
> - Swing for desktop apps
> - UI/FX for waba on Palm and PocketPC

Agreed.

> > because of the platform, but that is not really true.  (Okay, with a
> > dragonball, it is, but with a higher power handheld, no)
>
> Note that for high-end PDAs like IPaq, there are several VMs like Kaffe
> that work well with a 200MHz CPU with 32 Megs RAM. With low-cost platforms
> where both CPU and mem resources are low, you'll have to do compromises,
> anyway.

Run well is a matter of opinion.

> Achieving to build a flexible and open appliance around a CPU lik a
> DragonBall is essentially an economic issue, since the price, power
> consumption, low memory need, etc. have all together an impact on the final
> cost.

Well, they came together for those reasons a few years ago, and now there is 
a large user base.  If one were to design a brand new design, and didn't care 
about binary compability with current apps, they'd be insane to choose a 
DragonBall processor for their HWA implementation.  There are far more cost 
efficient vs. performance vs. power consumption processors in the marketplace 
now.  (All I want is a damn MMU..., is that too much to ask for? :)

Thanks,
Shane Nay.

_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/pgui-devel

Reply via email to