Home   Info   DevZone   Wiki   UsersWeb  |  MainWeb  |  InfoWeb  |  DevZoneWeb  |  SupportWeb
[ UserInterfaceWorkingGroups ] [ not logged in ] [ Web: Imported ] goto:  options [ get info on or edit ] [ login or new user ] [ list of topics, hubs & nodes, or recent changes ]

CommandLineInterfaceGroup

The Command Line Interface (CLI) group is responsible for determining the requirements and behavior of the default command line interface for JOS. This should be intended as a debugging and administrative tool -- it will likely be necessary for repairing damaged systems or configuring systems remotely.

TraditionalGraphicUserInterfaceGroup

The Traditional GUI group is responsible for designing a windowing system that mimics the traditional GUIs in place today -- Windows 95, X-Windows, the Macintosh, etc . . . It should be based on Sun's Swing component set, and support the "pluggable" look-and-feel. This includes defining a "JOS" look-and-feel for the Swing component set.

• GUIs should be totally based on JFC/Swing
• Possibly based on HotJavaViews (just an option)
• Preferably GUIs should be based on the JFC segmentation model (found in JFC documentation)
• L&F functionality directly from JFC/Swing

ExperimentalGraphicUserInterfaceGroup

The Experimental GUI group is responsible for designing a User Interface that reinvents the whole idea of a user interface. It is intended to prove the versatility of JOS's UI system, guarantee the design of JOS does not limit the UI in unexpected ways, and hopefully provide the computing community with the next insanely great UI.

ShellGroup

The Shell group is responsible for insuring the plumbing that makes the other UI's possible is in place. It should define a set of generic system services which serve all UIs, encourage cross-pollination of the other groups, and resolve differences between them.

• WindowingSystem should be written in 100% Pure java for the first release, meaning we can begin work on it NOW!!
• Preferably both TUIs and GUIs should be segmented into their Model/View/Controller sections for maximum reuse of code and stem from the same Model (jos.ui - for example)
• They should be at least swappable for the first release but maybe 'hot swappable' in the future
• GUIs should be totally based on JFC/Swing
• Version 1 possibly based on HotJavaViews (just an option)
• Preferably GUIs should be based on the JFC segmentation model (found in JFC documentation)
• L&F functionality directly from JFC/Swing

Other: WorkingGroups

Content of these pages are owned and copyrighted by the poster.
Hosted by: