<AWT Dev> Better support for external Toolkits/GraphicEnvs

[Roman Kennke]

Hi Phil,

> The changes you are talking about are probably far reaching and sound 
> somewhat like the fb-toolkit proposal itself.  This is tantamount to 
> replacing
> the entire AWT and 2D stack and I don't see that as a useful goal.

I don't know. I was able to get a small AWT Hello World program running
with the OpenJDK and the GTK peers in half an hour (basically extending
the GTK peers to implement some stuff in the peer interfaces that wasn't
implemented yet).

> As noted in my initial email to the fbtoolkit proposal, toolkits are not 
> pluggable, nor was
> there any design intent that they ever should be.  

There's the peer interfaces which doesn't seem so bad, even if there was
no design intent behind them. At least, in GNU Classpath land we could
live quite well with it, even to the extent that we had 3 different
working sets of AWT peers /GraphicsEnvs, each of them even supporting
their own widgets, graphics, font and image implementations. Granted, we
extended the peer interfaces at some points (mostly fonts), but nothing
'tantamount'.

I'll just post some patches and you tell me what you think, ok?

Cheers, Roman
-- 
Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org
aicas Allerton Interworks Computer Automated Systems GmbH
Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany
http://www.aicas.com   * Tel: +49-721-663 968-0
USt-Id: DE216375633, Handelsregister HRB 109481, AG Karlsruhe
Geschäftsführer: Dr. James J. Hunt