Corevisions wrote:
>
> hi .. i just read the ui discussion about widgets and have some
> questions and ideas about it ..(think they are not really finished so
> excuse me).
>
> first i want to give you my idea of how JOS should work ...
>
> - the first thing JOS should do on bootup is to initialize the desktop
> (like MacOS) so you have no text based views
I disagree. While I believe that a gui-only system is nice, many people
prefer text-based user interfaces or command-line interfaces. Plus,
they are much simpler to create and will give us something to test our
code on once the bare-bones system is ready.
> - with a special keycombination you can now enter the system-setup where
> you can add/remove drivers etc
Hmm... I don't know if this is necessary because JOS is supposed to
allow users to specify drivers while the system (gui/cli/etc) is
running. Most driver changes should not require a reboot or special
startup selection procedures.
>
> i think of a fully plugable system :
>
> ROOT
> |- driver
> | |- sound
> | | |- (driver) soundblaster
> | | |- (driver) MPU401 comp
> | | .
> | |
> | |- video
> | | |- (driver) VESA gfx
> | | |- (driver) OpenGL
> | | .
> | |
> | |- filesystem
> | | |- (driver) JOSFs
> | | |- (driver) FAT
> | | |- (driver) Amiga FFS
> | | .
> | .
> |
> |- ui
> | |- desktop
> | | |- (desktop) standard JOS desktop _OR_ (desktop) experimental
> 3D desktop
> | | .
> | |
> | |- l&f
> | | |- (l&f) Swing _OR_ (l&f) MacOS X Server _OR_ ...
> | | .
> | |
> | .
> .
There are already many packages specified... see the Packages page on
the JOS Wiki.
>
> this should be stored somewhere and all things should be implemented on
> startup
What are you trying to say? If you're referring to a registry, there is
already one in the making.
>
> of couse you will need interfaces like
>
> public class W9XlikeDesktop extends JOSDesktop
>
> or
>
> public class JOSFS_AmigaFFS extends JOSFileSystem
>
> - this should be the maximum the system should provide to the user. all
> other things should be plugged into it to asure
> a maximum of configurability
I agree that it should be maximally configurable, but I think it's a
little early to say what initial OOB configuration should be.
>
> sorry if it is not really part of the ui section.
> please give me a response and more of your ideas ...
>
> btw how exactly shold JADE work ? are there any links on the JOS page ?
AFAIK from discussions with Digigod, JADE is the underlying system upon
which all UIs rest. It provides things that are common among the UIs,
like receiving keystrokes, handling graphics devices, input devices, and
other output devices. The other UIs can be then defined using JADE as
the workbeast. For example, a Traditional GUI would ask JADE to put the
video card in graphics mode, and ask for a specific part of the screen
to draw on. It would not have to know how all of this is being done.
JADE is for UIs what OO is for imperative programming -- hiding all the
work behind a nice interface, and making it reusable.
Sean Cribbs,
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
