Difference between revisions of "Proposal by Knoxy"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Test of content again)
(Initial Publish)
Line 1: Line 1:
{| style="border: thin dashed #CC2222; padding:5px; background:#FFDAB9"
 
|-
 
| '''This page serves as a template''', so please do not edit this page unless you are on the Renaissance team. Your feedback and comments will be welcomed on the [mailto:ui@ux.openoffice.org ui@ux.openoffice.org] mailing list.
 
|}
 
 
__NOTOC__
 
__NOTOC__
  
= Design Proposal [Add Proposal Title] =
+
= Design Proposal - FLUX UI =
 
{{User Experience Community}}
 
{{User Experience Community}}
{| style="border: thin dashed #CC2222; padding:5px; background:#FFDAB9"
 
|-
 
| Please do not edit this page unless you are the original author. Your feedback and comments are welcome in the '''Comments '''section below or on the  [mailto:ui@ux.openoffice.org ui@ux.openoffice.org] mailing list.
 
|}
 
 
 
The following design proposal is part of the collection of design proposals for “Accessing Functionality”, which is part of Project Renaissance.
 
The following design proposal is part of the collection of design proposals for “Accessing Functionality”, which is part of Project Renaissance.
  
 
== Summary and Status ==
 
== Summary and Status ==
<span style="color:DimGray">How to use this template: Please write a short summary here to introduce the ideas in your proposal. For example, write a few sentences covering the highlights and the name of the proposed design. (Please delete this and all of the other gray explanatory text before you submit your proposal.)</span>
+
'''FLUX UI''', or '''FLUX User Interface''', is a user interface design proposal for OpenOffice.org initially developed by [[User:Josmar52789|Joshua Martin]], Stefan Roeben, and Mikko Lehmitsolo. FLUX UI was a winner of the 2008 Sun Microsystems Community Innovation Awards Program. The design is now being developed by [[User:Josmar52789|Joshua Martin]], [[User:Ak13|Adam W. Knox]], and Pranavrules. Three design principles guide the design's development:
  
Status: Request for Comments
+
* The document is the most important UI element.
 +
* Don't show the user what he/she doesn't need at the moment (context sensitivity).
 +
* Don't focus on a single UI element (i.e. Ribbon, Menus, Tabs) - use a hybrid of elements so that the information is displayed in the most appropriate way.
  
<span style="color:DimGray">After you consider the comments and questions in the comments section, revise your proposal for completeness and understandability. When you feel your proposal is ready for evaluation, please change the status above to “Proposal Complete”. </span>
+
Please know, this design is far from complete. It is our hope that even if this particular design is not implemented, a number of ideas might be collected from our thoughts on user interface design.
  
 
== Mockup ==
 
== Mockup ==
<span style="color:DimGray">Please add your main “wireframe” mockup. For example: A mockup which shows the functionality for adding a slide in Impress.
 
  
 
{| class="prettytable"
 
{| class="prettytable"
| [[Image:ProjectRenaissance DesignProposalCollection Template EmptyProposal.png|640px|thumb]]
+
| [[Image:Impress-proposal-layout-2.png|640px|thumb]]
 +
[[Image:Impress-proposal-mockup-2.png|640px|thumb]]
  
 
|}
 
|}
  
 
== Detailed Description ==
 
== Detailed Description ==
<span style="color:DimGray">This space is reserved for the detailed description of your design. Add anything you might find important for us to know. If you don't have any clue what this might be, then you will find some topics below.</span>
+
You can download our official Call for Design Proposals Presentation [[Media:Call_for_Design_Proposals_-_Impress.odp|here]].
 +
 
 +
 
 +
* '''Utility Bar''': Consists of the most common "File Menu" options.
 +
 
 +
''new file, open file, save, save as, print''
 +
 
 +
 
 +
* '''Document Bar''': Consists of the most common “Standard Toolbar” commands. These are commands that must be accessible at all times as their usage is unpredictable. Also, this “toolbar” will function as a drag/drop/remove toolbar to which users can add their own commonly used commands.
 +
 
 +
''Undo, Redo, Spell Check, Cut/Copy/Paste, Zoom, Gallery, Navigator''
 +
 
 +
 
 +
* '''FLUX Bar''': Completely context-sensitive “toolbar” that allows various options depending on the current workspace
 +
 
 +
''Ex. User clicks on rectangle drawing -- Then... Dynamic Options Menu displays the 3D tools, background, styles + formatting, etc.''
 +
 
 +
''Ex. User has nothing selected -- Then... Dynamic Options Menu displays Slide Layout options, Master Page options, slide background, etc.''
 +
 
 +
 
 +
* '''Slide List''': List of slides in the current presentation. This is merely an implementation of the current “Slides” pane.
 +
 
 +
 
 +
* '''Slide View Options''': Drop down list of available slide views. Though we know a tab-based method is far more common, we thought that something “drop down based" was more efficient for this design.
 +
 
 +
''Ex. Normal, Outline, Notes, Handout, Slide Sorter''
 +
 
 +
 
 +
* '''Tabs (Horizontal)''': Designed as a replacement for menu-driven approach. One tab for each group of related commands and features. ''Note: This is NOT a MS Office Ribbon knock-off. This is a traditional tab-based UI element for inserting objects and performing tasks similar to the UI of Dreamweaver MX.''
 +
 
 +
''Ex. Tab “Insert” would have buttons: Insert Slide, Insert Image, Insert Chart, Insert Symbol, etc.''
 +
 
 +
''Ex. Tab “Publish” would have buttons: Export, Export to PDF, Send Document as E-mail''
  
* <span style="color:DimGray">'''Describe dynamic behavior''': The mockup above is something static. To better illustrate what will happen on the screen, describe what actions would be taken by the user and what would appear on screen.</span>
 
* <span style="color:DimGray">'''Explain the rationale and assumptions''': If you decided to go for a certain concept, then please explain why you chose this.</span>
 
* <span style="color:DimGray">'''Highlight particular design ideas and alternatives''': A concept usually incorporates many individual ideas. If you think certain ideas are really unique, then please highlight them. And if you think that there were other really good ideas which could not be implemented at the same time, tell us about them.</span>
 
* <span style="color:DimGray">'''List issues and open questions''': Please list any issues you are aware of and open questions. Do not worry if your proposal or concept isn't perfect. If you have discovered any stumbling blocks or worries, then please provide this information right from the start. Maybe the team can help find answers/solutions.</span>
 
  
== Additional Material and Mockups ==
 
<span style="color:DimGray">Please share everything you might think is important to better understand your proposal. Perhaps you also have other ideas which are not directly related to “Accessing Functionality”? You might add further documents, Internet links, or additional mockups - e.g. showing a workflow or different states of the software.</span>
 
  
 
== Author or Team Working on This Proposal ==
 
== Author or Team Working on This Proposal ==
Line 47: Line 66:
  
 
|-
 
|-
| <span style="color:DimGray">Real Name</span>
+
| <span style="color:DimGray">Joshua Martin</span>
| <span style="color:DimGray">OpenOffice.org Login Name</span>
+
| <span style="color:DimGray">[[User:Josmar52789|josmar52789]]</span>
  
 
|-
 
|-
| <span style="color:DimGray">Real Name</span>
+
| <span style="color:DimGray">Adam W. Knox</span>
| <span style="color:DimGray">OpenOffice.org Login Name</span>
+
| <span style="color:DimGray">[[User:Ak13|ak13]]</span>
  
 
|}
 
|}

Revision as of 02:55, 11 May 2009


Design Proposal - FLUX UI

ux-ooo-logo-rgb-129-61.png

ux.openoffice.org

Quick Navigation

Team

The following design proposal is part of the collection of design proposals for “Accessing Functionality”, which is part of Project Renaissance.

Summary and Status

FLUX UI, or FLUX User Interface, is a user interface design proposal for OpenOffice.org initially developed by Joshua Martin, Stefan Roeben, and Mikko Lehmitsolo. FLUX UI was a winner of the 2008 Sun Microsystems Community Innovation Awards Program. The design is now being developed by Joshua Martin, Adam W. Knox, and Pranavrules. Three design principles guide the design's development:

  • The document is the most important UI element.
  • Don't show the user what he/she doesn't need at the moment (context sensitivity).
  • Don't focus on a single UI element (i.e. Ribbon, Menus, Tabs) - use a hybrid of elements so that the information is displayed in the most appropriate way.

Please know, this design is far from complete. It is our hope that even if this particular design is not implemented, a number of ideas might be collected from our thoughts on user interface design.

Mockup

Impress-proposal-layout-2.png
Impress-proposal-mockup-2.png

Detailed Description

You can download our official Call for Design Proposals Presentation here.


  • Utility Bar: Consists of the most common "File Menu" options.

new file, open file, save, save as, print


  • Document Bar: Consists of the most common “Standard Toolbar” commands. These are commands that must be accessible at all times as their usage is unpredictable. Also, this “toolbar” will function as a drag/drop/remove toolbar to which users can add their own commonly used commands.

Undo, Redo, Spell Check, Cut/Copy/Paste, Zoom, Gallery, Navigator


  • FLUX Bar: Completely context-sensitive “toolbar” that allows various options depending on the current workspace

Ex. User clicks on rectangle drawing -- Then... Dynamic Options Menu displays the 3D tools, background, styles + formatting, etc.

Ex. User has nothing selected -- Then... Dynamic Options Menu displays Slide Layout options, Master Page options, slide background, etc.


  • Slide List: List of slides in the current presentation. This is merely an implementation of the current “Slides” pane.


  • Slide View Options: Drop down list of available slide views. Though we know a tab-based method is far more common, we thought that something “drop down based" was more efficient for this design.

Ex. Normal, Outline, Notes, Handout, Slide Sorter


  • Tabs (Horizontal): Designed as a replacement for menu-driven approach. One tab for each group of related commands and features. Note: This is NOT a MS Office Ribbon knock-off. This is a traditional tab-based UI element for inserting objects and performing tasks similar to the UI of Dreamweaver MX.

Ex. Tab “Insert” would have buttons: Insert Slide, Insert Image, Insert Chart, Insert Symbol, etc.

Ex. Tab “Publish” would have buttons: Export, Export to PDF, Send Document as E-mail


Author or Team Working on This Proposal

Author / Team Member Contact (OpenOffice.org login name, used for email)
Joshua Martin josmar52789
Adam W. Knox ak13

Comments

Community members, this is where your comments and questions concerning completeness and clarity should be written. Please add your OpenOffice.org login name to let us contact you via email.

Your space :-)

Personal tools