Ryan Heise wrote:
> Again, removeToolbarWidget() is very similar to disposeWindow(). For the
> same reason, I believe it should be a method on the model (and
> controller). I think you will find that some widgets (including
> DesktopWidget) will need to define /some/ public methods to handle
> direct interactions between views (widgets). I have found this
> unavoidable, but those methods are subordinate to the methods provided
> by the model (and controller). They would be needed, for example, to
> allow a ToolbarWidget component to be added (in AWT terms) to its
> Container. This is a direct view <-> view interaction that requires
> public widget methods.
we could have a very abstract model, it doesnt even need to be aware of
the components its using, we could represent them as Rectangles to it.
all it would have is a view rectangle (the screen) and a stack of
rectangles that it was in charge of z-ordering and the like. the
controller would handle conversion between windows and rectangles and
the view (DesktopScreen) would render accordingly.
this could be reused by many things, even a UI that doesnt use AWT or
Swing to do windowing (for whatever reason). which bring up something
Ive been wondering about it is possible to make text peers for the AWT
but it translates badly, it could be possible for us to design our own
TWT (think about it) for TUI's, it could extend our classes for basic
CLI stuff. is that good or bad though? (eitherway it should be packaged
outside of JADE org.jos.twt)
oh, there should also be a maximize/restore thing in the wherever that
would go since it is different to the OS then having it resized to
screen size and placed so it covers everything.
> There is probably very little you can decide about the view interfaces
> at this point in time. When you start to consider how the controllers
> and models come in to play, your design will probably change completely.
> I definately think it is easier to start designing from the model end.
> Even then, your design will change a bit when you start to consider how
> the view fits into the picture. But at least when you get there, you
> will have already thought about the foundations of your MVC system.
you may be right, but we could at least get a basic idea of what we need
to put them in, but more importantly (and Ive tried to stress this) of
which ones to include that list I gave was far from complete, and some
of them should have different, more appropriate, names.
we have all sorts of people who have used allsorts of UI's, we can think
of more widgets as part of our ADW package (abstract desktop widgets?
org.jade.adw and the swing ones in org.jade.adw.simple)
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
