Aaron M. Renn wrote:
> > Classpath has some of swing done. I don't know about Kaffe..
>
> Classpath has a bit of a GTK look and feel for Swing done. The work
> completed is fairly minimal.
>
> Park of the problem is that you need a 1.2 AWT for Swing to run on top of
> and the 1.2 AWT looks substantially more complicated than the 1.1 AWT.
> Swing itself is huge. Perhaps has big as the entire 1.1 API combined.
Although people now tend to think of Swing as part of JDK1.2, it actually
predates that significantly. I'm still using Swing code under IBM's
JDK1.1.x for Linux quite routinely. I have a feeling that there may be
some /minor/ changes in the interactions between Swing and AWT under
JDK1.2, but I don't think they're huge. If people want to start work on
a Classpath Swing implementation now, I don't see any reason why they
shouldn't -- there's quite a bit of groundwork to be done before anything
would be testable, anyway.
What priority you attach to this is another matter: I'd hope that it might
be possible to get Sun's Swing implementation running on top of Classpath
AWT, and this might be a reasonable stepping stone towards a completely
free Java2 implementation.
Thomas
