Java UI Woes

Subclassing List won't work in the way you want.  This is because in
the AWT model, all drawing is done by the peer, and while you can draw
over the top of the peer the peer doesn't know you did any drawing and it
is free to redraw over the top of any drawing you do, and further all
behavior is determined by the peer.

What you *CAN* do is subclass Component, and create your own lightweight
components.  Be warned that with the ancient version of Java that is this
Personal Java stuff, mixing heavy/light weight components is tricky and
bound to not work.  Therefore, if you take this route, you may need to
write your own lightweight component library.  It's not terribly hard and
you certainly don't need to go as overboard in throwing in kitchen sinks
and garden hoses and bedroom suites and whatnot as the Swing Team did in
making Swing.

- David Herron


> From: [email protected]
> To: [email protected]
> Subject: [Zaurus-devel] Java UI Woes
>
> I am making an app that requires a Table UI component. If I could use
> swing I would be all set with a JTable, but I can't seem to find a good
> equivalent in PJ 1.1. List doesn't cut it, so basically I am looking at
> subclassing list and making my own table, but to be honest I don't
> really want to waste my time if a workaround is available somewhere.
> Implementing the table myself will seriously eat up time I could be
> spending on my app. Any help would be appreciated :)
>
> --Matt



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf