> A CLI isnt going to have a taskbar, a XUI might not. JADE cant assume
> there is a taskbar, if there was a taskbar its only interaction would be
> that it uses JADE to get things like the process manager (to create the
> list of tasks) so a taskbar is part of the UI and is part of a JADE
> plug-UI but is not part of the core JADE its self. also, what if system
> y doesnt have Swing? it would need an AWT taskbar. the answer is all the
> desktop widgets must be designed via interface.
Oh, I know. There will most definitely be many user interfaces, and
each could have (or not) its own taskbar widget. Certainly a CLI won't
have one.
>
> public interface Taskbar extends DesktopWidget {
> //bla bla bla
> }
>
> Defaults for building the "default JOS UI" will be implemented in Swing
> of course. the best part is a single component could take on more then
> one widget function like: "X implements TaskBar, Clock".
>
> infact we should make (abstract?) Swing components of more general use
> then extend them for the default UI
Good idea!
I wasn't speaking of _THE_ taskbar widget for JOS, just working on a
prototype so that we can figure out what is involved, what APIs need to
be created or modified, etc.
Sean Cribbs
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
