Sean Cribbs wrote:
>
> Regier Avery J wrote:
>
> > On the issues with initializing to the proper toolkit, I think Ryan Heise
> > has solved some of those problems. See:
> > http://www.progsoc.uts.edu.au/~rheise/projects/SwingToolkit/
>
> I see you have reached the heart of the problem: The toolkit cannot be
> changed once one has been loaded. It's an issue with Sun's code that I
> don't know how to deal with. I can post a snippet of where the problem
> exists in java.awt.Toolkit, if it's legal to post.(?)
>
> I have Heise's code. It doesn't work on the new JDK.
Hi Sean. When I wrote SwingToolkit, JDK 1.2 was not available for Linux.
And I'm not surprised that it doesn't work considering that it is
incomplete. I really just got it to the stage where I demonstrated that
such a thing could be done, and hoped that other people would finish it.
It's good to see you're aiming to go all the way.
As Regier pointed out, I have solved some of the initialization problems
associated with Toolkits. The README file explains the approach I've
taken. Feel free to take a look.
I will have to read the list archives to get up to speed on this
discussion (I fell off the gui list when we changed list servers, and
I've just rejoined). I will take a look at your source code some time.
There is another Swing based window manager out there called Shark
(available on http://www.gjt.org/). The author has also written his own
native Graphics class to draw directly to the screen rather than reusing
java.awt.Window.
--
Ryan Heise
http://www.progsoc.uts.edu.au/~rheise/
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
