[null_]

Is Java always slower? Got a problem with a GUI being too slow. Would eVC++ be a lot faster? how is the J++ performing compared to C++ and which one do I want to use to get the most out of the PDA? Need to create a GUI-based program networking over bluetooth, with very good graphical performance. Need to do demanding things like scrolling lists of controls. Anyone got the experience to tell what I need? Learning a new lang is no problem.
Many thanks for any advice!

(Using iPaq h3970 with PPC 2002)

[null_]

Is Java always slower? Got a problem with a GUI being too slow. Would eVC++ be a lot faster? how is the J++ performing compared to C++ and which one do I want to use to get the most out of the PDA? Need to create a GUI-based program networking over bluetooth, with very good graphical performance. Need to do demanding things like scrolling lists of controls. Anyone got the experience to tell what I need? Learning a new lang is no problem.
Many thanks for any advice!

(Using iPaq h3970 with PPC 2002)

[Janak Parekh]

Sounds to me like you should be using eVC++, which is downloadable for free. I know people have gotten Java + SWT working, which is a bit faster than Java + AWT on Pocket PCs, but you're still not likely going to be able to access the Bluetooth APIs unless you use JNI (and is that even supported on WinCE?)

--janak

[null_]

I tried SWT already and sadly, it's far too slow. (see Java... thread)
Thanks for the advice and the link!
cheers!

SWT is probably a good choice for some applications using a simple GUI that does not depend on fast updating... for others comitted to Java. I think I'm leaving the ship now. eVC++ here I come!
8)

[hudsonmobile]

eVC++ is the right choice for fast GUI -- within eVC++ you have a choice between using MFC-style window classes or straight Win32 calls. I did my application in straight Win32 because that is what I had experience in, but I am not sure if there is a performance penalty for using the window/control classes in MFC. With the MFC-style approach, it is probably easier (less lines of code) to make controls with custom behaviors and transfer data to and from controls...