> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Emmel > > John Keiser wrote: > > > > > I would love to see Classpath being used somewhere. > > > > --John > > I'd like to re-announce a project I've been working on for the > last few years. > > I have and AWT toolkit based on top of Swing. > For a standard AWT release it depends on and implementation of > Frame, Window and Graphics. Plus some minor native dependencies in Image. If it is based on top of Swing, how could we possibly help?? We're still working on AWT, we're nowhere near Swing. > <snip> > The reason I'm bring this up is it would be beneficial to be > able to tune the > AWT to > handle a Java based Windowing System. Suns current AWT contains numerous > assumptions > which do not hold in the case of a Java Windowing System. > This is an interesting point. What assumptions do you mean, for example? > What I would need from Classpath is the base AWT classes. > If I can get production quality results out of a combined effort > then at the > minimum. > The Classpath classes are ready to run on top of a Java based > Windowing System. > This is Aaron/Paul's area, I don't know where they are yet. Is your stuff not production quality? > I can't make any promises about open source my project but if there's and > interest > and commitment in Java based Windowing Solutions now or in the > future I can > certainly make a very strong case. > This is interesting too ... but you have to realize that if you want to work with this project the Open Source will have to be LGPL? Why would your company want to do that, anyway? Not that I'm against it, but for curiosity's sake: are the proprietary solutions not working well enough, or do you want to do away with dependency on a company? > Since it currently depends on Swing I personally don't see Open > Source being a > big issue until > Classpath develops a Swing replacement. > Again, though, what do you propose? To run Classpath but add Sun's Swing stuff? I'm just having technical difficulties understanding the plan here. > What I can do is as Classpath AWT implementaion comes a long I > can test it > agianst my > peers It should Just Work tm. Later maybe more. > I love that idea especially. Testing good. And it would be nice to be able to debug the AWT before it is complete, which it sounds like your AWT is capable of doing. > And earlier open source (LGPL) version of the code is available > at the GJT > under > org.gjt.shark. > That code base is now being reviewed by the JOS www.jos.org project. > I'm no longer working on the Open Source code base. > Since I've been able to work full time on the later > closed source version I've managed to bring the work basically > to production quality within the limits of Sun's JVM and class libraries. > So what are the limits you're running into? Since I'm not working on AWT, I can't make commitments, obviously, but I am curious about this. --John Keiser
