Thomas Down <[EMAIL PROTECTED]> writes:
> 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 think Aaron might have been confused. We know (collectively) that
Swing was originally implemented on top of 1.1 AWT and since the
introduction of 1.2 has some bindings to the Java 2D API which is only
available in 1.2. Sun has thus far continued to release 1.1
compatible versions of Swing, probably just to satisfy corporate
customers.
> 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.
Part of the problem with Swing has been the lack of a real
specification for it. I sent email to the void, Sun, but received no
reply to it concerning the lack of documentation needed to properly
create a clean room version. Without the documentation, the task then
pretty much falls to creating lots and lots of test programs to
generate the needed data. One of the interesting places to start work
on Swing is simply to try extending the Basic PLAF (and overriding
everything) to determine programatically how things work when
documentation fails which is my reason for working on the GTK PLAF to
begin with.
I think Sun has released some tutorials which also contain useful
information for more than just using Swing to create applications.
Brian
--
Brian Jones <[EMAIL PROTECTED]>
