-----Original Message-----
From: DigiGod Q Frasch� <[EMAIL PROTECTED]>
To: Sean Cribbs <[EMAIL PROTECTED]>
Cc: jos ui mailing list <[EMAIL PROTECTED]>
Date: Friday, July 16, 1999 11:48 AM
Subject: Re: [JOS-UI] peer-ui mappings
<snip>
>But maybe the window quasicomponent/peer shouldnt talk directly to the
graphics device but instead to a handy abstraction called Screen, this would
encaps. the Screen (duh), provide stuff like the
>colorModel and screensize to the toolkit. it could handle stuff like window
drawing (all that boring redraw crap no one wants to do) via a "default"
child (DesktopScreen?). And as I said before the
>screensaver would be passed this directly so it could play with the
desktop.
How does this "Screen" abstraction differ from Java2D's
GraphicsConfiguration, GraphicsDevice, and GraphicsEnvironment classes? It
seems to me that these contain all the information/fuctionality needed for a
Screen. We just need a way to have the Toolkit use our current
GraphicsDevice instance for the given system's hardware.
I haven't looked too deeply into this, but I think this may be a good place
to start.
-Matt
>Cheers,
>DigiGod
>_________________________
>[EMAIL PROTECTED]
>AIM:DigiGod 86
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
