Re: [Usability]A Challenge: Describe the GNOME 4.0 interface.

[Dave Bordoley <bordoley msu edu>]

I'm in a dreamy mood so here I go :)

Key elements to my "ideal" ui are:
1. Document/Object oriented UI. 
Applications no longer exist. Instead there are only views. Views are
pluggable into the desktop shell. Also since the ui is object oriented,
new views can be built upon existing views, or by combining views (for
example a code editor inherits from from a generic text editor).

2. Database file system
Hierarchies are no more. All folders are the result of database queries
based on mime types, file content (ex. you could create a folder
containing all files with the term 'gnome'), and other persistent mime
data (ex. all files with certain emblems).

3. Templates
New files are created from templates. You open a template file to create
a new document. Upon opening a template you are prompted to provide a
name for the document. The document is instantly saved and is added to
any folders for which it meets the criteria. In the case where it does
not meet any search criteria, it is added to the desktop.

The basis of this ui is the desktop shell. This shell provides a
component based view of your computer and data. For folders,
icon/list/column component views are used. For text files a text editor
view is used and so on. There are no applications anymore.
 
> Describe as many specifics as you have time to.
> E.g.,
>   The GNOME menu

No longer exists, because we no longer have applications.

>   Application menus, toolbars, etc.

Some basic ideas: 

1. All document windows have rename and duplicate in the file menu.
Choosing rename actually renames the currently viewed file/object.
Duplicate creates a copy of the file, opening another window with a view
of it.

2. Instant save. Enough said, we already have instant apply this is the
next step.

3. The elimination of cut copy and paste from the folder view, to be
replaced with a shelf type metaphor. (i told you I was dreamy)

4. Toolbars are sparingly used. The are only used in views where they
provide actual utility.

>   Theme

I have no problem with providing the ability to theme as long as it
doesn't interfere with overall usability. I favor the idea of theme sets
(ie. themes which affect the whole interface). New themes are created by
duplicating templated themes and altering their characteristics in the
theme editor view.

>   Help
>   Documents and document handling
>   Audience

Human beings who are not concerned with the inner workings of a
computer.

>   Panels

I haven't thought too much about this. I'm still very unclear about how
the panel plays into the overall ui. I as others, find the nature of
panel applets as first class objects a little weird.

> 
> 
> Don't say someone else is on crack.
> 
Yeah I'm probably on crack, I don't care :)

dave