Proposal by Rodrigo Carvalho

From Apache OpenOffice Wiki
Revision as of 11:17, 11 May 2009 by Rcsilva83 (Talk | contribs)

Jump to: navigation, search

Design Proposal [Add Proposal Title]


Quick Navigation


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 mailing list.

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

Summary and Status

The purpose of this proposal is to create a non-intrusive contextual interface with a steep learning curve.

The focus is on:

  • dynamic components that morph by context;
  • non-intrusive notifications;
  • take simple decisions to user;
  • familiar UI;

The goals are to:

  • ease of learning
  • reduce amount of clicks to perform activities
  • reduce time to find features

The design directives are:

  • minimize clutter and maximize consistency (similar elements are grouped and positioned in similar ways)
  • minimize redundancy and maximize relevancy (required information is revealed on demand)
  • minimize recall and maximize recognition (visual decision aids are provided when they are beneficial)

The constraints are:

  • do not interrupt user by showing modal windows
  • always apply default behavior for actions
  • always show only relevant tools for each activity (e.g. never show table editing buttons when writing text)

Status: Request for Comments


Please add your main “wireframe” mockup. For example: A mockup which shows the functionality for adding a slide in Impress.

ProjectRenaissance DesignProposalCollection Template EmptyProposal.png

Detailed Description

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.

  • 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.
  • Explain the rationale and assumptions: If you decided to go for a certain concept, then please explain why you chose this.
  • 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.
  • 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.

Additional Material and Mockups

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.

Author or Team Working on This Proposal

Author / Team Member Contact ( login name)
Rodrigo Carvalho User:Rcsilva83


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

Your space :-)

Personal tools