> > I have been looking into it. Note the classpath stuff is very different > > from the current kaffe AWT implementation. It would break the current AWT > > support. So I have to port the current stuff to the Classpath format. This > > will take some time. > > i think porting kaffe's current implementation to the classpath > format as you've called it will basically involve creating a set > of lightweight peers in some kaffe.awt.whatever package and move > all the drawing from the widgets in java.awt into the different > peers afterwards? And if so, how would this break the current > AWT support? It will be totally different, yes, but we wouldn't > loose any of the supported backends, would we?
True. I have started work on the X window lightweight peers. I shoudl finish it in about a week. _______________________________________________ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
