Renaissance/Design Proposals for “Accessing Functionality”
|Please do not edit this page unless you are on the Renaissance team. Your feedback and comments will be welcomed on the firstname.lastname@example.org mailing list.|
The Project Renaissance team now invites you to unleash your creativity to find a new concept to “Accessing Functionality” in Impress, the presentation application.
The wiki page you are now reading describes the first call for proposals of design ideas.. As you may know, the mission of Project Renaissance is to “Create a User Interface so that OpenOffice.org becomes the users' choice not only out of need, but also out of desire”. Due to the incredible complexity of the overall task, it is essential to define ambitious but realistic sub-tasks which can be achieved more easily. Thus, the first sub-task will be to improve how functionality is accessed in Impress.
Basically, anyone can participate and contribute new and innovative design ideas. In the first call for proposals, it is important to accumulate, without interference, as many independent design ideas as possible that can later contribute to the creation of a new UI concept for OpenOffice.org Impress.
After the proposals have been submitted and evaluated, the design ideas with the greatest potential will be integrated into one modular design concept that will be evaluated with respect to the design goals and the design directives. Then, the design concept will be refined through iterative cycles of evaluation and modification until the whole concept or parts of it reach a maturity level that is ready for high-fidelity prototyping. High-fidelity prototypes will help us mimic and test fundamental behavior of the design concept before anything actually gets put into OpenOffice.org.
So, the current focus is to carefully develop the initial ideas. Why carefully? The changes will have an enormous impact on all of our users – both our existing and future user base will be heavily affected. So we take responsibility for about one hundred million people. Consequently, once the proposals have been collected, they will have to be evaluated in an objective manner– nothing should be based on opinions of individuals.
Until now, a lot of data has been collected within the research phase of Renaissance to better understand what people think about OpenOffice.org, to know who our users are, and to know what they want to accomplish with our office suite. That data is the basis for a set of goals, constraints and documents which will – hopefully – help you to develop your design proposal. Find data here: Data Collected in Phase 1
Well, what's next?
- If you want to participate, then please keep reading. :-) Instructions and schedule follow.
- If you have general questions concerning Project Renaissance, then please visit the official Project Renaissance wiki page.
- If you have questions that the wiki page above didn't provide answers for or you would like to make comments about these instructions or the details of the call for proposals, then please send a mail to the email@example.com mailing list.
- Check the User Experience planet to get the latest news and track the progress.
Thank you for making OpenOffice.org even better!
The following table contains the official schedule and provides some procedural information. Basically, there is a certain time frame for community members to privately work on their own ideas. These ideas are to be made public as design proposals published on the wiki on a given date. If anything in the proposal is unclear, the authors will be asked for clarification. That's it so far. Currently, we may only guess what the outcome of this call for proposals will be, so we won't look at next steps yet.
|2009-04-20||Call for Design Proposals|| Starting with this announcement, members of the community are officially invited to propose designs based on their ideas.
The team of Project Renaissance will provide media and information covering goals, constraints and how to proceed.
|...||Work Phase||Individuals or teams use their creative energy to develop their own designs. The design ideas are kept secret to avoid undesired harmonization between the different submissions ... fresh ideas are most valuable in this phase.|
|2009-05-11||Publish the Design Proposals|| The authors publish the design proposals on separate pages in the OpenOffice.org wiki. That makes it possible to check and compare the proposals.
|2009-05-12||Review the Submissions|| The proposals can be commented by the whole community and the contributors are asked to act upon requests regarding completeness and clarity of their proposals.
|2009-05-25||Final date for Revised Versions||This is the due date for the authors to present their revised design proposals in the wiki.|
Creating a Design Proposal
In order to participate in submitting a design proposal, please follow these steps:
- Use the template for creating a design proposal and work out your design (see Design Proposal Template).
- Send a short email to firstname.lastname@example.org to announce that you have started working. This is so that everyone knows how many people are working on proposals and how they can be contacted.
- Work while keeping your proposal contents secret until the date for publishing the design proposals (see Schedule).
- Publish your proposal on the wiki and announce it with a link on email@example.com (see Design Proposals Submitted and Design Proposal Wiki Template)
If you have any questions or comments at any time, please send a mail to the firstname.lastname@example.org mailing list.
Design Proposal Template
Template for developing a Design Proposal including e.g. goals and graphic styles: Design Proposal Template (OpenOffice.org Impress File)
Although any ideas are welcome, the following principles shall give you an idea of what we have in mind for the collection of design proposals. If you have any questions concerning their meaning, then please ask on ux-discuss.
- The purpose of the collection of design proposals is to brainstorm for as many proposals as possible without interference
- The focus is set on:
- information architecture (e.g. grouping of elements, labeling of elements, integration of elements, prioritization of elements)
- interaction design (e.g. task mapping, work flow)
- The focus is not on visual design (e.g. gradients, shadows, transparency)
- The goals are to:
- help users to find and use essential functionality more easily
- help users to gain in expertise quickly
- help users to create eye-catching documents in less time
- The design directives are to:
- 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 remove functionality in OpenOffice.org that is currently available
- do not add functionality in OpenOffice.org that is not available
- be visually scalable (the target screen size is 1.024 x 768 pixels, but if you want you may even think of netbooks 1.024 x 600 … large screens 2.560 x 1.600)
- The required UI ingredients are
- global navigation (e.g. menu)
- local navigation (e.g. toolbars)
- contextual navigation (e.g. context menu)
- supplemental navigation (e.g selecting slides)
- The task focus is on Impress
- creating and editing of presentations
- managing presentations
- reviewing presentations
- running presentations
Frequently Asked Questions
Question: May I choose my favorite application to create the design proposals?
Answer: We prefer an OpenOffice.org application such as Draw or Impress. However, you may use anything else that you are comfortable with.
Question: Which file format may I choose for my proposal?
Answer: You may choose any graphics file format which can be embedded in our wiki, e.g. working with OpenOffice.org and exporting the vector graphics into PNG.
Design Proposals Submitted
The following table will list the design proposals which have been submitted. Proposals will be added to this list once they have been published (refer to Schedule).
|Proposal Title||Wiki Page||Author / Team Members|
|Wiki Template||Renaissance/Design_Proposals_for_“Accessing_Functionality”/Design_Proposal_Wiki_Template||The Renaissance Team|
|DaVinci||Proposal by Jaron Baron||Jaron Baron|
|Complete Sidebar Design||Proposal by Constantin Bürgi||Constantin Bürgi|
|Martinů||Proposal by Johannes Eva||Johannes Eva|
|Iced Coffee||Proposal by Miroslav Mazel||Miroslav Mazel|
|Style Editing Directly at Toolbars||Proposal by Jörg Sievers||Joerg (Jogi) Sievers|
|FLUX UI||Proposal by Knoxy||Joshua Martin, Adam W. Knox|
|...||Proposal by Michel Renon||Michel Renon|
|Professional Looking Presentation||Proposal by Jörg Wartenberg||Jörg Wartenberg|
|Simple UI||Proposal by Rodrigo Carvalho||Rodrigo Carvalho|
|Contextual Menus & Toolbars||Proposal by Frank Loehmann||Frank Loehmann|
|Contextual Toolbars||Proposal by Loehmann Jansen||Frank Loehmann and Christian Jansen|
|...||Proposal by Cinly Ooi||Cinly Ooi|
|Tabbed & Menu-Based Navigation||Proposal by Andreas Bartel||Andreas Bartel|
|Customizable "containers"||Proposal by Juan Canham||Juan Canham|