"Aaron M. Renn" <[EMAIL PROTECTED]> writes:
> The Classpath TODO list as of 2000/04/16
>
> -- Modify Classpath build to support libgcj out of the box. Ideally
> the gcj folks could simply include a stock classpath in one of their
> distribution subdirectories, have their master configure run a configure
> on Classpath the appropriate arguments, and everything would build.
I believe the idea was for occasional imports into libgcj from
Classpath? I'm not familiar enough with the requirements of being
part of gcc builds to deal with this one if it is what you really
want.
> -- Write Mauve (http://sourceware.cygnus.com/mauve/) tests for those
> classes that don't have them.
How are awt tests to be handled in mauve?
> -- java.awt.image: Unsure of status but partially implemented.
Some of the filters and such are not implemented... of course Kaffe
doesn't either. Anyone know a good book on image manipulation? The
spec leaves a lot to be desired with regards to specificly how these
should be implemented.
> -- Write an implementation of Swing. This is a big job and should
> probably be a separate, non-Classpath project that can be shared
> with Kaffe. Please write to the mailing list if you are interested
> in helping with this. ([EMAIL PROTECTED])
I've been working off and on on javax.accessibility (the documentation
being the slowest part). I'll commit it when I'm done and have tested
it against Sun's implementation.
--
Brian Jones <[EMAIL PROTECTED]>
