Difference between revisions of "Framework/Specification/Customize MenuAndContextMenuDialog"
(→Context Menu and Menu customization dialog) |
(→References) |
||
Line 23: | Line 23: | ||
| '''Product Requirement, RFE, Issue ID''' (required) | | '''Product Requirement, RFE, Issue ID''' (required) | ||
| available | | available | ||
− | | [http:// | + | | [http://www.openoffice.org/issues/show_bug.cgi?id=115794 i115794] |
|- | |- | ||
| '''Accessibility Check''' (required) | | '''Accessibility Check''' (required) |
Revision as of 08:20, 26 November 2010
Specification Status | |
Author | Carsten Driesner (cd) |
Last Change | 25. Nov 2010 |
Status (Help) | Standard |
Abstract
The customization dialog for menus is not that intuitive as it could be. Thanks to the work from Ariel Constenla-Haile during the Internship 2010 context menus are now also customizable by XML files. Therefore a better design which covers context menus and menu bar customization is needed.
Contents
References
Reference Document | Check | Location (URL) |
Prerequisites | done | |
Product Requirement, RFE, Issue ID (required) | available | i115794 |
Accessibility Check (required) | done | See accessibility section for check list |
Test case specification (required) | available | TCS Find Toolbar |
IDL Specification | does not apply | |
Software Specification Rules | done | |
Other, e.g. references to related specs, Product Concept Document | available | specification: search toolbar |
Release Roadmap OOo 3.3 | available | http://wiki.services.openoffice.org/wiki/OOoRelease33 |
Contacts
Role | Name | E-Mail Address |
Developer | Carsten Driesner | cd@openoffice.org |
shizhoubo(robertzhou) | robertzhou@openoffice.org | |
Yan Wu | wuyan.ooorg@gmail.com | |
Quality Assurance | Stefan Baltzer | sba@openoffice.org |
Jörg Skottke | Joerg.Skottke@Oracle.com | |
Documentation | Uwe Fischer | Uwe.Fischer@Oracle.com |
Icon Design | Stella Schulze | Stella.Schulze@Oracle.com |
User Experience | Christoph Lukasiak | Christoph.Lukasiak@Oracle.com |
Jaron Kuppers | jaronbaron@gmail.com |
Acronyms and Abbreviations
Acronym / Abbreviation | Definition |
<WYSIWYG> | <What You See Is What You Get> |
Motivation
From the 'usage tracking' data of the 'find & replace' dialog we have learned that 76% of oo user just want to search inside the text, so we have to propose a fast & easy way to do so. Also it was often mentioned that the search & replace dialog covers the search area in an annoying way, so we must found an other solution for it. The other search settings like 'match case' etc. are used less than 0.1%, so we decided to leave them out in this toolbar, but like the replacing function they will still stay available in the find & replace dialog.
Detailed Specification
The 'Find' toolbar is a standard toolbar containing a text search field, a next and previous button. It is located right next to the 'application standard' toolbar, is active by default and behave like every other toolbar (d&d, docking etc.).
By clicking into the search field, the info text disappear and the search text can be inputted. After entering the search text, the search can be started by hitting the return key on keyboard (+ shift for backwards search) or pushing the 'next/previous' button. If anything is found, the first result is selected and can be edited or the next button can be clicked (if selected) for searching for the next result. If nothing is found or it is searched to the end of the document, you get an info dialog similar to the behavior of the 'find & replace' dialog, like in all other cases, even if it works independent.
- Autocomplete involves the program predicting a word or phrase that the user wants to type in without the user actually typing it in completely. This feature is effective when it is easy to predict the word being typed based on those already typed, such as when there are a limited number of possible or commonly used words, or when editing text written in a highly-structured, easy-to-predict language.
- History remember former search strings (string listbox) .. often you search for the same words several times, so it can make sense to remember them (especially it they are long and complicated) and to make them available over a listbox in example to save the input of same phrases again and again. The history is deleted after closing the document (for privacy reasons) and only available in the document it was inputted.