User Experience/Proroposal DataPilot byIBM
|
|
|---|
|
Quick Navigation
Team |
| Late Submission! This proposal was submitted after the official deadline. Thus, it might not have been reviewed sufficiently by the community. |
DataPilot UX Design Proposal by IBM
The following design proposal is part of the collection of design proposals for “Accessing Functionality”, which is part of Project Renaissance.
Contents
Summary
Symphony team start to develop/enhance DataPilot feature since Symphony 1.1, and still working to improve it in Symphony 2.0. To improve user experience to use DataPilot, we designed&developed new user interface in the releases, including: - New DataPilot table: Show a predefined new table to users avoid the meaningless table which have nothing. - DataPilot panel: Users can work with fields there and update the changes automatically. - Dialogs: Improve the information architecture and UI controls of the dialogs, e.g. field options, sort. - Filter: A filter panel make users can filter items of fields directly in the DataPilot table. Some useful functions are added here, e.g. search items, show only the current item. Users can also set to show "Top n" items in this panel. - New DataPilot table style: We improve the predefined DataPilot table style, make the table is clear in visual. - Editing and reading mode: When users focus on the DataPilot table, it will be editing mode and users can get the DataPilot panel and fields buttons within table automatically. Users can modify the table conveniently via these UI. When users focus out of the table, it will be reading mode and the DataPilot panel and fields buttons within table will be hided automatically, so that users can show the DataPilot table to others clearly.
New DataPilot table
|
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 (OpenOffice.org login name, used for email) |
| Real Name | OpenOffice.org Login Name |
| Real Name | OpenOffice.org Login Name |
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 :-)
