Sean Cribbs wrote:
Hilary Cheng wrote:
>
> Hi Sean,
>
> >> I didn't mean to be that harsh! There are two identifiable reasons why
> >> his code doesn't work on my JDK. The first is that all of the swing
> >> packages are named com.sun.java.swing.*, whereas Java2 uses
> >> javax.swing.*. The second is the same reason why I had trouble with
>
> I have ported to javax.swing. It got no problem to port. Since nothing has
> been depends com.sun.java.swing.
I assume that would work. I was just too lazy to edit the source.
>
> >> creating my own toolkit: java.awt.Toolkit maintains a reference to the
> >> first initialized toolkit, preventing a subsitute toolkit from doing the
> >> job. I agree with your disgust over Sun's lack of backwards and
> >> forwards compatibility, but that's not the type of discussion (or
> >> argument) I meant to start!
>
> Could we rewrite ClassLoader so that we can load the AWT Toolkit be4 the
> default one ?
Actually, that may not be necessary. There's an idea brewing in my head
right now about how to overcome this major difficulty. I'll get back to
you when I have something concrete.
>
> Last things, would JOS depends on JDK1.2 or JDK1.1 ? Two JDK's Graphics
> Handling are not the same.
I would hope that JOS will support the latest JDK, whatever version it
will be, when it is released. For now, I think we should assume JDK1.2
-- it has more functionality and is mostly backwards compatible.
Sean Cribbs
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
