Ok, I'm looking around and we are actually doing pretty well on putting
together a Java 1.1 compatible API. If we date the start of the Classpath
project to when I started coding java.net back in March of 1998, we are just
a little bit over a year old. Here's what we've got done in that year:
java.awt.datatransfer - Done 1.1, mostly complete for 1.2
java.awt.event - Done for 1.2
java.beans - Done for 1.1, being updated for 1.2
java.io - Done for 1.2
java.lang - Done for 1.1, partially done for 1.2
java.lang.reflect - Done for 1.1
java.math - Done for 1.1
java.net - Done for 1.1, mostly complete for 1.2
java.security.acl - Done for 1.2
java.security.interfaces - Done for 1.2
java.sql - Done for 1.2
java.text - 90% done for 1.[12] (I'll count it as finished)
java.util - Done for 1.2
gnu.java.awt.peer.gtk - AWT peer set done for 1.1
Japhar VM Integration Layer - for Japhar 0.07 and above.
Unfortunately, Japhar 0.08 (the latest release) does not work with
Classpath. Chris Toshok has corrected this in the latest CVS version, so
Japhar 0.09 should have full Classpath support back when it is released
(whenever that might be).
The following are works in progress
java.awt.image - 1.1 in progress (Paul Fisher)
java.security - 1.1 in progress (Mark Benvenuto)
java.util.zip - 1.1 in progress (Loren Peace)
The most critical of these is java.util.zip, which Mr. Peace said was 90%
done in January, but he has disappeared again. I need to find him so we can
get that completed. We cannot support running from a zip/jar file until we
do. If anyone has a lead on where he might be, let me know.
Mark Benvenuto has written a huge portion of java.security which is waiting
to be checked in as soon as he gets CVS access, which should be any day.
Paul, what is up with that?
The following classes have not been started:
java.applet
java.awt
java.rmi.*
Way back when we had Greg Smith ([EMAIL PROTECTED]) listed as doing
java.applet, but I haven't heard from him in months. Greg, if you are
alive, speak up.
Paul Fisher has a lead on an RMI implementation that we might be able to
adapt to our use.
So what does this mean? It means we are very close to having 1.1 completed.
Once java.util.zip and java.security are done - which will hopefully be
soon - we will have a complete 1.1 runtime library (with a lot of 1.2
functionality) ready to go with the exception of the seldom used RMI
portion.
Here is how I would like to see us proceed. Basically, once we get those
two packages in and Japhar puts out another release that works with us, I
want to release Classpath 0.01. This should be usable for all non-AWT
applications. From there, I want to start banging on it hard with whatever
we can find and focus on stability and filling in the holes in our
implementation. Horrible performance problems should also be fixed if they
exist (and they do in at least two instances). With the 0.01 release (and
perhaps some fixes on top of that) hopefully we can start have people other
than the developers work with this stuff. This will hopefully find more
bugs, make us more robust, etc. The AWT will be migrated into this when it
is completed. Ditto for RMI.
In short, I would like to concentrate on putting out a high quality 1.1
release before taking on too much of 1.2. Let me know what you all think of
this.
Could everyone also speak up and let us know what you are working on. As
the amount of "uncharted territory" shrinks, the chance of us duplicating
effort goes up. I'd particularly be interested in hearing from Greg Smith
and Loren Peace.
If there are other people/things I have left out, I apologize. Please speak
up. (I know I did not mention the servlet implementation for example).
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
