Sven de Marothy wrote: > Ok, I've been looking into the issue of our AWT peer > interface now that I've been running my peers on Classpath > in earnest. > > The goal here is to try to bring our peer interface as close to Sun's > as possible. And simplify things for potential peer-authors. > [...] > > Summary: So, my opinion: Keep most of the font stuff and the robot > stuff. Get rid of the rest, and we'll have an interface which is both > closer to the JDKs, and simpler. > > Comments?
I very much agree. My peers are only toys at the moment, but I ran into many of the same issues. Especially the fact that the GTK event model is integrated in EventQueue is very bad. > Method: createEmbeddedWindow () > Comment: What's an EmbeddedWindow and why do we need this as > part of the peer interface? I'm not sure, but I think this is used for Applets that have to live inside a non-Java window. Regards, Jeroen _______________________________________________ Classpath mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath
