Sean Cribbs wrote:
> OK, but we will have to make an assumption at this point that the
> simplest peers, i.e. Component, Container,
> Window, etc. will not have calls to native libraries and will instead
> call some Java-abstracted graphics hardware device. I don't know if
> that part of the project has been finalized yet. Also, it would be
> useful to have some spec on the Shell interface. In trying to create a
> skeleton for the JOSToolkit, I realized that some of the functionality
> there should be things that could be accessible from any UI (e.g.
> beep()).
>
> Some thought should definitely go into the interface to graphics devices
> soon, because with a spec for the graphics device, we could create the
> Toolkit, peers, and everything in a matter of weeks. For now, we can
> settle with relegating the most fundamental component/graphics stuff to
> a default toolkit.
exactly, although I think window is the only one that should have to talk to the
graphics device directly, the way AWT/Swing draws that would be the only thing
nessecary. also, and Ive said it before,
we should have swappable titlebars (that is a Swing FrameComponentUI) in our
quasicomponent/peer for the frame class (since not all plafs would support this we
should have it change to the default
(that is JOS) L&F's titlebar so you dont have something like a window titlebar on a
mac window (because you know they'd just get into a fight)).
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.
Another point of buisness, all this stuff is lowlevel JADE (if you dont know what Im
talking about see JADE on the Wiki) and JADE, being the UI, isnt really part of the OS
so should it be in org.jos?
I dont think so, org.jade would be more appropriate since it is a JOS-only app and it
would be a pretty big, no point getting it all mixed up with JOS (its easier for
everyone this way)
Cheers,
DigiGod
_________________________
[EMAIL PROTECTED]
AIM:DigiGod 86
_________________________
Quote of the Moment:
Thus spake the master Ninjei:
"To the intelligent man, one word, to the fleet horse
one whip, to the well-written program, a single
command"
_________________________
Prank of the Moment:
Using the conferencing feature of your office phone, dial
one Induhvidual, then while it's ringing dial another and
conference them together. Put your own phone on mute
and listen to see how long they'll make small talk before
figuring out that neither one placed the call.
O-
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
