Another poll (sorry)

OK, subsequent to my previous castings-around, I've decided to go with the 
J2ME interface for mobile phones and Internet-enabled PDAs. I've put together 
a working GUIcomms transport layer, and I'm now set to work on the user 
interface. Therein lies my dilemma.

On the one hand, we have J2ME's built-in LCDUI package. This allows for a 
number of forms, each with a list of components such as text boxes, guages, 
etc. There are no buttons - this is handled by "actions" associated with a 
form. These are bound to "soft buttons" on mobile phones, and a row of button 
components along the bottom of the screen on Palms.

Pros:	Universal, loads quickly
Cons:	Would make RB a bit ugly and slow to use, especially on PDAs which 
could do better

On the other hand, we have kAWT, a small version of the full-blown Java UI 
package. This has the full works - forms, buttons, layouts, tab panes, 
everything.

Pros:	Looks good and would be easier/faster, especially on large-screen 
devices (PDAs, Blackberry, stylus phones)
Cons:	Loads less quickly than LCDUI, increases MIDlet size beyond the maximum 
for very low-end phones (the full toolkit alone is a 100k JAR, and the demo 
takes about 200k of memory).


As I see it, this is a choice between an application which will run on most 
Java phones and PDAs at a "usable" level, and one which will run on 
higher-end/newer phones and all PDAs and is easier to use.

Votes, please? Who would prefer what, and why?

Meredydd
-- 

Everybuddy project maintainer
http://www.everybuddy.com/

MSN:     [email protected]
AIM:     blip109
Yahoo:   modula7