Hey John, If you're looking for a system GUI, I believe we are still in PRE-alpha stage (not everything is implemented yet, but we've got windows showing and widgets showing). If you want to integrate now and work with text for a while until we complete integration of AWT and AWT peers, then I think it's a great idea. The non-GUI side of Classpath is pretty dang solid. Status: java.util, java.net and java.io work great. java.lang and java.lang.reflect work fine with Japhar and should be easy to plug into JOS (it makes no assumptions about VM architecture except that it supports JNI). java.beans is solid (I have heard people have taken it out of Classpath and used it instead of Kaffe's), and java.text is at least working (I am not sure if it is complete, Aaron?). I think Aaron and Paul are the best people to ask about AWT status. Paul (with James Blair) is working on GTK+ peers, and Aaron is working on the AWT classes. I do not know how well it's all working, but we are getting closer to complete. Note that, as far as I know at least, Classpath is not being used in a large-scale system yet. People have verified that their servers work without a hitch on Japhar+Classpath, but that's all I've heard in terms of use. I always have the energy to talk and explain things (and it's something I can do during downtimes at work--I can't code or it would be owned by the company), and I can get you started integrating if you want to do it. I can't guarantee how much time I can spend, but I will at the *least* answer questions and fix bugs and problems with Classpath. If major architectural problems come up, I will need to defer to my esteemed colleagues. My time is severely cramped right now. I would love to see Classpath being used somewhere. --John
