Ryan Heise wrote:
> I don't quite see the usefulness of this. For example, when you
> implement the Swing or AWT widgets, they will handle rectangles and
> z-ordering in their own way.
>
> If you were suggesting the idea in response to my observation that there
> needs to be some view <-> view interactions, are you trying to eliminate
> these interactions? I think when you get around to implementing your
> Swing widgets, you will find that the most sensible thing to do is to
> have direct view <-> view interactions when they are needed. For
> example, when a JComponent needs to be graphically added to a JPanel.
> Just keep in mind that these view <-> view methods are internal
> implementation methods, and the real methods to add a ToolbarWidget to a
> DesktopWidget are in the controller and model classes.
no, no this isnt what I meant at all. I was reffereing to the windows on
the desktop.
the Model is a collection of rectangles each with a z-order the
"screens" rectangle being a constant last. each window on the desktop is
represented as a rectangle.
the controller is implementation specefic in this case, AWT (which Im
betting would be 99.99% all cases, if not more) it mediates between the
view (the desktop) and the "genderless" model (the rectangles),
translateing the Windows.
the desktop draws itself according to the commands of the controller
which is a translator for the model. (of course the desktop also has to
handle drawing the background and the icons and the screensaver if your
inactive long enough)
I see the benifit not being to us but to those who can use the same
Model since they need, for X reason, to use a different set of
components then AWT. And both the model and controller (and possibly
even the view if done properly) can be reused by the standard Swing/AWT
TGUI's
> PagerWidget - control for virtual desktops
> MenuWidget - for example, you could dock a start menu to the
> TaskBarWidget.
>
> I'm thinking we should call it a system menu, not a start menu.
PagerWidget is a good widget but not to be included in JADE, we decided
awhile ago that a UI/extension to JADE was to be provided that handled
virtual desktops by proxing itself (in the guise of a PUI) between JADE
and the real UI's. the coolest benifit of this being the ability (if
done properly) to plug in X different UI's (assuming support for all) in
the vw's
win95 style context menus would implememnt MenuWidget's too, as would
the menubar thingy on macs (which would also be a toolbar since its
attached to the desktop btw (what is that thing called again?)).
system menu, here here. start menu? start what? at least when you call
it system menu people know what your talking about.
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
