Apache OpenOffice Wiki - User contributions [en]

Specification search toolbar

2009-07-25T02:54:39Z

Pgan002:

This page is the current design of a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is a tool bar which will provide quick text searching. It includes highlighting all search occurrences, backwards searching, forward searching, case-matching, whole word matching, and a close button. It can be closed via the close button or by pressing a keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change - 2009-05-18
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is a tool bar which will provide quick text searching. It includes highlighting all search occurrences, backwards searching, forward searching, case-matching, whole word matching, and a close button. It can be closed via the close button or by pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| Li Meiying,Zhu Lihua
| limeiying@redoffice.com,zhulihua@redoffice.com
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text, and to avoid a window hiding the content of the document.

== User Scenarios ==
Currently OpenOffice.org users must use the search dialog to search text. When the search dialog obscures the document content, the user must move the search dialog via the cursor.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which provides quick search functionality without obscuring user content, as an alternative (NOT a replacement) for the existing search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching algorithms of the current search dialog. It won't interfere with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1) is located below the address tool bar and can't be moved. The search tool bar can made visible by pressing Ctrl+F. It is very simple and only provides text searching and no case matching or whole word matching functionality. It includes backward and forward searching and a count of the found search text. The Search tool bar is organized into a number of buttons or labels which are horizontally arranged.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozilla's Search Tool bar (Figure 2) is located above the status bar and can't be moved. The Search tool bar can be made visible by pressing Ctrl+F. It is is organized into a number of buttons which are arranged horizontally. The mouse can be used to click the buttons and every button has a state.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar (Figure3) shall be located above the status bar and will be immovable. It can made visible by pressing Ctrl+F1. It contains the common tool bar items including BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describes what the purpose of the tool bar is and what should be entered into the Search Text Field. The static text label is “Find.” It should support multilingual properties.

=== 2. Search Text Field ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| When the search toolbar is enabled, it is always enabled
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Search Text Field is a text box where users input their search text string. If the search text does not match any strings in the document as defined by the search criteria, the text box background color should be set to gray as shown (circled) in the following figure.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text in the Search Text Field
|
|-
| '''Disabled:'''
| if there is no text in the Search Text Field
|
|-
| '''On Click:'''
| Forward searches the current document for the search text
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. When triggered, the button forward searches the current document for the search text. To inform the user that the last instance of search text within the document is found, the Dynamic Text Info2 changes to “reached end of document, continue from top” as shown (circled) in the following figure.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text in the Search Text Field
|
|-
| '''Disabled:'''
| if there is no text in the Search Text Field
|
|-
| '''On Click:'''
| Backward searches the current document for the search text
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. When triggered, the button backward searches the current document for the search text. To inform the user that the last instance of search text within the document is found, the Dynamic Text Info2 changes to “reached end of document, continue from end” as shown (circled) in the following figure.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text in the Search Text Field
|
|-
| '''Disabled:'''
| if there is no text in the Search Text Field
|
|-
| '''On Click:'''
| All instances of the search text, within the document, will be shown highlighted and selected
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type. When triggered, all instances of the search text, within the document, will be shown highlighted and selected (as demonstrated in Figure 7). The “search all button” will not need to change states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| When the search toolbar is enabled, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Future text searches via the are case-sensitive
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case Check Box is a check box button. When the check box is in a true state, text searches are case-sensitive. If no instance of the search text exists in the document, the Dynamic Text Info2 will show “phrase not found” as shown (circled) in the following figure.

=== 7. "Whole Word" CheckBox===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| When the search toolbar is enabled, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
| None
|
|-
| '''Checked:'''
| searching text will match the whole word to find in the current document.
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Whole Word Button is a check box button. When the check box is in a true state, text searches match the search text to delimited strings, as opposed to any occurrence of the search text string. If no instance of the search text exists in the document, the Dynamic Text Info2 will show “phrase not found” as shown (circled) in the following figure.

=== 8. "Count information" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Show count information of the searching text in the current document
| <Comment>
|}

The "Count Message" label is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the "Count information" Label will be shown , and tell user count of the searching text in the current document.

=== 9. "feedback" Label ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| None, it is dynamic stirng, it show different message according to result of searching text
|
|}

The feedback is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the 9."feedback " Label and 8."Count information" Label would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
The current searching dialog in the OOo.
The search toolbar of the Mozilla firefox.

= Time schedule =

{| width="80%" border="1" cellpadding="2"
!width="20%"|Milestone
!width="20%"|Goal
!width="20%"|Planned
!width="20%"|Achieved
|-
|| 1 || First specification ready || 31.05.2009 || ---
|-
|}

[[Category:Features]]

Calc/Drafts/Show Formula Syntax

2009-07-25T01:45:14Z

Pgan002: /* Rationale */

== Design for a new feature in Calc: "Show Formula Syntax in tip help" ==
===Function description===
According to the request of the to-do list in Calc OOo community, the feature is to show formula syntax in tip help in Calc. This feature would make the user get immediate feedback when a cell formula is being edited, in addition to the function selection above the cell, show some input hints (like the syntax of the function that is edited) in a tip help window below the cell 
[http://wiki.services.openoffice.org/wiki/Image:Show_Formula_Syntax_Specification.odt the Specification of this new feature]

===Rationale===
This feature has been discussed extensively in a [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1270 thread on the UX discuss mailing list]. Several specific variations of and additions to the original specification have been discussed, including:
* In tip help, highlighting the currently expected function argument using surrounding space characters (also referred to as "suggestion 2").
* In tip help, highlighting the currently expected function argument using a special character, e.g. a downwards arrow ("suggestion 8").
* In tip help, explicitly stating the currently expected function argument using natural language ("suggestion 3").

The above three points tried to work around the fact that formatting currently isn't supported in tip help.

* In edited cell, using suggest-as-you-type autocompletion to inform about function syntax and aid formula editing ("suggestion 4").
* Using tip help syntax info combined with a programming-environment-like suggest-and-pick interface (comparable to [http://help.eclipse.org/help33/topic/org.eclipse.jdt.doc.user/tips/jdt_tips.html#editing_section Eclipse's Content Assist]).

In the discussion of these rather specific suggestions, the need was recognized to step back and analyze the formula manipulation process as a whole. What lies behind this requirement? What functions do people use? What are they trying to achieve? This "big picture" analysis will include a re-evaluation of the current procedures and components.

Because this analysis will take time, Maoyg is going to implement "suggestion 8" in the meanwhile.

See also [http://www.openoffice.org/issues/show_bug.cgi?id=86856 the original suggestion on OOo's bug tracker] and
[http://wiki.services.openoffice.org/wiki/Image:symbols.odt the Specification of the symbol]

[[Category:Calc|Draft/Show Formula Syntax]]
[[Category:To-Do]]
[[Category:Draft]]

Calc/Drafts/Show Formula Syntax

2009-07-25T01:41:41Z

Pgan002: /* Design Rationale */

== Design for a new feature in Calc: "Show Formula Syntax in tip help" ==
===Function description===
According to the request of the to-do list in Calc OOo community, the feature is to show formula syntax in tip help in Calc. This feature would make the user get immediate feedback when a cell formula is being edited, in addition to the function selection above the cell, show some input hints (like the syntax of the function that is edited) in a tip help window below the cell 
[http://wiki.services.openoffice.org/wiki/Image:Show_Formula_Syntax_Specification.odt the Specification of this new feature]

===Rationale===
This feature has been discussed extensively in a [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1270 thread on the UX discuss mailing list]. Several specific variations of and additions to the original specification have been discussed, including:
* In tip help, highlighting the currently expected function argument using surrounding space characters (also referred to as "suggestion 2").
* In tip help, highlighting the currently expected function argument using a special character, e.g. a downwards arrow ("suggestion 8").
* In tip help, explicitly stating the currently expected function argument using natural language ("suggestion 3").

The above three points tried to work around the fact that formatting currently isn't supported in tip help.

* In edited cell, using suggest-as-you-type autocompletion to inform about function syntax and aid formula editing ("suggestion 4").
* Using tip help syntax info combined with a programming-environment-like suggest-and-pick interface (comparable to [http://help.eclipse.org/help33/topic/org.eclipse.jdt.doc.user/tips/jdt_tips.html#editing_section Eclipse's Content Assist]).

In the discussion of these rather specific suggestions, the need was recognized to step back and analyze the formula manipulation process as a whole. What lies behind this requirement? What functions do people use? What are they trying to achieve? This "big picture" analysis will include a re-evaluation of the current procedures and components.

Because this analysis will take time, Maoyg is going to implement "suggestion 8" in the meanwhile.
See http://www.openoffice.org/issues/show_bug.cgi?id=86856 
[http://wiki.services.openoffice.org/wiki/Image:symbols.odt the Specification of the symbol]

[[Category:Calc|Draft/Show Formula Syntax]]
[[Category:To-Do]]
[[Category:Draft]]

Calc/Drafts/Show Formula Syntax

2009-07-25T01:41:32Z

Pgan002: /* This function can be described as follows: */

== Design for a new feature in Calc: "Show Formula Syntax in tip help" ==
===Function description===
According to the request of the to-do list in Calc OOo community, the feature is to show formula syntax in tip help in Calc. This feature would make the user get immediate feedback when a cell formula is being edited, in addition to the function selection above the cell, show some input hints (like the syntax of the function that is edited) in a tip help window below the cell 
[http://wiki.services.openoffice.org/wiki/Image:Show_Formula_Syntax_Specification.odt the Specification of this new feature]

===Design Rationale===
This feature has been discussed extensively in a [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1270 thread on the UX discuss mailing list]. Several specific variations of and additions to the original specification have been discussed, including:
* In tip help, highlighting the currently expected function argument using surrounding space characters (also referred to as "suggestion 2").
* In tip help, highlighting the currently expected function argument using a special character, e.g. a downwards arrow ("suggestion 8").
* In tip help, explicitly stating the currently expected function argument using natural language ("suggestion 3").

The above three points tried to work around the fact that formatting currently isn't supported in tip help.

* In edited cell, using suggest-as-you-type autocompletion to inform about function syntax and aid formula editing ("suggestion 4").
* Using tip help syntax info combined with a programming-environment-like suggest-and-pick interface (comparable to [http://help.eclipse.org/help33/topic/org.eclipse.jdt.doc.user/tips/jdt_tips.html#editing_section Eclipse's Content Assist]).

In the discussion of these rather specific suggestions, the need was recognized to step back and analyze the formula manipulation process as a whole. What lies behind this requirement? What functions do people use? What are they trying to achieve? This "big picture" analysis will include a re-evaluation of the current procedures and components.

Because this analysis will take time, Maoyg is going to implement "suggestion 8" in the meanwhile.
See http://www.openoffice.org/issues/show_bug.cgi?id=86856 
[http://wiki.services.openoffice.org/wiki/Image:symbols.odt the Specification of the symbol]

[[Category:Calc|Draft/Show Formula Syntax]]
[[Category:To-Do]]
[[Category:Draft]]

Calc/Drafts/Show Formula Syntax

2009-07-25T01:41:10Z

Pgan002:

== Design for a new feature in Calc: "Show Formula Syntax in tip help" ==
===This function can be described as follows:===
According to the request of the to-do list in Calc OOo community, the feature is to show formula syntax in tip help in Calc. This feature would make the user get immediate feedback when a cell formula is being edited, in addition to the function selection above the cell, show some input hints (like the syntax of the function that is edited) in a tip help window below the cell 
[http://wiki.services.openoffice.org/wiki/Image:Show_Formula_Syntax_Specification.odt the Specification of this new feature]

===Design Rationale===
This feature has been discussed extensively in a [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1270 thread on the UX discuss mailing list]. Several specific variations of and additions to the original specification have been discussed, including:
* In tip help, highlighting the currently expected function argument using surrounding space characters (also referred to as "suggestion 2").
* In tip help, highlighting the currently expected function argument using a special character, e.g. a downwards arrow ("suggestion 8").
* In tip help, explicitly stating the currently expected function argument using natural language ("suggestion 3").

The above three points tried to work around the fact that formatting currently isn't supported in tip help.

* In edited cell, using suggest-as-you-type autocompletion to inform about function syntax and aid formula editing ("suggestion 4").
* Using tip help syntax info combined with a programming-environment-like suggest-and-pick interface (comparable to [http://help.eclipse.org/help33/topic/org.eclipse.jdt.doc.user/tips/jdt_tips.html#editing_section Eclipse's Content Assist]).

In the discussion of these rather specific suggestions, the need was recognized to step back and analyze the formula manipulation process as a whole. What lies behind this requirement? What functions do people use? What are they trying to achieve? This "big picture" analysis will include a re-evaluation of the current procedures and components.

Because this analysis will take time, Maoyg is going to implement "suggestion 8" in the meanwhile.
See http://www.openoffice.org/issues/show_bug.cgi?id=86856 
[http://wiki.services.openoffice.org/wiki/Image:symbols.odt the Specification of the symbol]

[[Category:Calc|Draft/Show Formula Syntax]]
[[Category:To-Do]]
[[Category:Draft]]

User Experience/Activities

2009-07-25T01:06:59Z

Pgan002: /* Latest Features */

{{User Experience}}
This page lists all User Experience activities and projects, and points to all OpenOffice.org feature specifications. The UX team has contributed to each of them as the user experience part is mandatory for every iTeam working on a new feature. So a main part of the User Experience Team work is done inside these specifications. Feedback is always welcome! Send your feedback to the iTeam lead and/or UX representative stated in a specification or use the [mailto:discuss@ux.openoffice.org UX discuss mailing list] to post your feedback.

==Current Activities==
The current section list all currently running/or recent work on specifications and proposals.

===Calc===
====Short/Mid-Term Planning====
The new [http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=22000 quarterly review process] allows to concentrate our efforts on the [http://wiki.services.openoffice.org/wiki/2008_Q2_Review_of_Spreadsheet_Project most important issues for Calc].

====Latest Features====
* [http://specs.openoffice.org/calc/features/Solver.odt Solver Implementation]
* [http://specs.openoffice.org/calc/features/Selection_Visualization.odt New Selection Visualization]
* [http://specs.openoffice.org/calc/features/Page_Margins_Specification.odt Resizeable Margin on Page Preview]
* [http://specs.openoffice.org/calc/features/Collaboration.odt Collaboration]
* [[Calc/Drafts/Show Formula Syntax]]

===Draw/Impress===
* [[Draw_Tables|Tables in Impress]]
* [[Export_Resolution_Draft2|Increase Export Bitmap Resolution]]

===Mid-Term UX Activites===
* The [[Renaissance]] project: “Create a ''User Interface'' so that OpenOffice.org becomes ''the users' choice'' not only out of ''need'', but also out of ''desire''”.

==Long-Term UX Activities==
Make OOo '''the''' desired productivity application

==Further Proposals==
* [[User_Experience/StartCenter|Start Center Enhancement]]
* [[User_Experience/Grand Concept|The Grand Concept]]
* [[User Experience/NewUser|New User Dialogue]]
* [[User_Experience/DirectManipulationSnippets|Direct Manipulation Snippets]]: Direct manipulation of document objects or information on the document itself.
* [[Notes2]]: The revision of the Notes in Writer. Some functionality will be available in OpenOffice.org 3.0.
* The [[User_Experience/Improved_Options|Improved Options]] activity: an attempt to improve the currently rather scary options dialog.
* The [[User_Experience/Improved_Styles|Improved Styles]] activity: an attempt to improve the user experience with styles in Writer.
* [[User Experience/Command search|Command search]] - user types the name of a command such as a menu entry and executes it, without having to search in the menu hierarchy

==OpenOffice.org Feature Specifications==
* [http://specs.openoffice.org/ui_in_general/index.html User Interface in General]: Specifications for Toolbars, Wizards, Widgets etc.
* [http://specs.openoffice.org/ui_term/index.html User Interface Terminology]: Specifications that deal exclusively with text on the UI.
* [http://specs.openoffice.org/appwide/index.html Application Wide]: Specification which affect all OpenOffice.org modules.
* [http://specs.openoffice.org/g11n/index.html G11n]: General globalization-related specifications
* [http://specs.openoffice.org/writer/index.html OpenOffice.org Writer]: Specifications for the text document module.
* [http://specs.openoffice.org/calc/index.html OpenOffice.org Calc]: Specifications for the spread sheet module
* [http://specs.openoffice.org/impress/index.html OpenOffice.org Impress]: Specifications for the presentation modulemodule
* [http://specs.openoffice.org/draw/index.html OpenOffice.org Draw]: Specifications for the drawing module
* [http://specs.openoffice.org/chart/index.html OpenOffice.org Chart]: Specifications for the chart module
* [http://specs.openoffice.org/math/index.html OpenOffice.org Math]: Specifications for the formula module
* [http://dba.openoffice.org/specifications/index.html OpenOffice.org Base]: Specifications for the database module
* [http://specs.openoffice.org/ide/index.html OpenOffice.org IDE]: Specifications for the basic & dialog editor
* [http://specs.openoffice.org/installation/index.html OpenOffice.org Installation]: Specifications for the installers

'''Specification Template''':
The specification template can be downloaded from here: [http://specs.openoffice.org/collaterals/template/2.0/OpenOffice-org-Specification-Template.ott OpenOffice-org-Specification-Template.ott]. You can also create a specification based on the [http://wiki.services.openoffice.org/wiki/Specification_Template wiki template].

File:OO command bar proposal.png

2009-04-16T05:13:11Z

Pgan002: uploaded a new version of "Image:OO command bar proposal.png": Slightly improved mockup

Mockup of the proposed command search facility. It is shown in the menu bar, although there is discussion about putting the search in the help menu for the MacOS version of OO.

User Experience/Project Administration

2009-01-31T07:46:14Z

Pgan002: /* Feedback Email to New Members */ replaced pre-formatted text by indentation so that the lines wrap to fit the window

{{User Experience}}

= Introduction =
This page provides information for the administration of the User Experience project, especially for the team leads. The information is collected for various reasons, e.g. improving transparency in project decisions or acting as a knowledge base for current and future project leads.

= Communication on the Mailing Lists =
* If emails are sent from non-registered users to the UX mailing lists, then the emails will be published on the UX mailing list (non-registered user: user's email-address is not subscribed to UX mailing list). The mails will be manually administered by the UX mailing list administrators. ([http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1661 Request], [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1675 Decision])
* Information may be presented to the UX team on a regular basis, e.g. a quarterly email to the UX mailing lists containing open topics or administrative reminders. If there is more urgent information, then the UX team is fine with an information email at any time. ([http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2167 Request], [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2294 Decision]) If there are any decisions to be made by the UX team, then two weeks should be enough for collecting the votes.

= Registration of new UX Team Members =
To become a UX team member it is necessary to register on the OpenOffice.org collaboration platform CollabNet and to request membership in the UX project (membership: observer role). Besides that, the UX project proposes additional steps to provide information about the user and to get in contact.

== Documentation on „How To Join“ ==
The wiki page [http://wiki.services.openoffice.org/w/index.php?title=User_Experience/Community/How_To_Join How To Join] comprises the information about how to get an UX team member.

== Feedback Email to New Members ==
The following text describes an email which is sent to the new UX team members. The email is sent by the UX administrator who approves the request for membership. It is sent directly after the approval to the requesting user (addressee: 'username' and added '@openoffice.org').

Goal:

* Encourage users to finish the procedure on “How To Join”. (Giving early feedback is always good.)
* Inform the user about the existence of the procedure “How To Join”. (Users may know from other projects how to request a membership in CollabNet. But they may be not aware of the UX specific procedure “Ho To Join”.)

Constraints / Content:

* The system CollabNet does not support automatically generated emails after approval. The UX administrators have to send this email manually.
* The wording should be friendly and cooperative.
* The impression of getting “spam” or unwanted information should be avoided.
* Feedback will not be directly offered, because ...
** the email is sent from the personal email address from the UX administrator(s). People may just ask by replying to that email adress.
** help is offered at the wiki page containing the “How To Join” information. That page refers to the corresponding UX mailing lists.
* The UX email signature “core values” described at [http://wiki.services.openoffice.org/wiki/User_Experience/Project_Strategy/External_Communication#The_Email_Signature External Communication] is used.

Email subject:

:Welcome! OpenOffice.org User Experience Team Membership.

Email body:

:Hello,

:Thank you for your interest in the OpenOffice.org User Experience project. Your request for an User Experience team membership has been approved.

:Being a new member in our administrative system means that you've done the "First Step: Administrative Stuff" in our procedure "How To Join" (link below). To finalize your team membership, please continue with the next step in our recommended procedure.

:If you currently don't know what we are talking about, then please have a look at the information "How To Join" (link below). There you will find information on how to register and how to get in contact with us. Thanks a lot!

:How To Join: http://wiki.services.openoffice.org/wiki/User_Experience/Community/How_To_Join

:See you later,

:The User Experience Project Administrators

:The fine print: Please note that this email has been sent manually from one of our User Experience Project administrators. You get this mail because you requested a membership in the OpenOffice.org User Experience team. This email is not part of a newsletter or any other information you will receive regularly.

:---
:Usability * Productivity * Enjoyment

:OpenOffice.org User Experience Team
:http://ux.openoffice.org

User Experience/StartCenter

2008-12-27T07:44:42Z

Pgan002: /* Historical Perspective */

{{User Experience}}
= Introduction =

OpenOffice.org is separated into single applications like Writer, Calc, Draw and Impress, which could be started directly from the operating system start panel. If the OpenOffice.org executable is started directly OOo shows the start module, always shown if no document is loaded. The start module has no value for the user on start-up, but keeps OOo loaded if the last document has been closed and a new one is generated. The plain start module makes it difficult start OOo from a link on the desktop to gain visibility on the Macintosh platform.

So a new StartCenter is needed to welcome the user. The “welcome” implies that is very important for the experience of the user, because:

* ... it is the first element the user might see (besides the download and installation procedure).
* ... it is an essential part of OpenOffice.org's visual identity.
* ... it creates a first impression on the features and the usability of OpenOffice.org.
* ... it should encourage the new user to work with OpenOffice.org.

== Development ==
The development of the new StartCenter has begun and is open for community discussion. A first version of it will be part of OpenOffice.org 3.0. After that, this start center could be further extended from version to version. New ideas can be added in section Collection of Ideas.

== Terms and Definitions ==
The following graphics contains terms and definitions which might be helpful for the ongoing discussion.

[[Image:UX StartCenter Definitions.png|center]]

A discussion has been started if another name but "StartCenter" may make more sense. You find it at [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1295 ux-discuss Message 1295].

== Issues ==

* '''[http://www.openoffice.org/issues/buglist.cgi?email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=startcenter&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query Extended Issue List]''' with all entries having the description "StartCenter" independent of their status, priority, ...
* [http://www.openoffice.org/issues/show_bug.cgi?id=90815 Issue 90815] [StartCenter] Provide configuration option to deactivate StartCenter

= StartCenter for OpenOffice.org 3.0 =
This first step of the development, targeted for inclusion in OpenOffice.org 3.0, defines the integration into the operating system and a first welcome dialog within the former backing window.

* The specification for the StartCenter is located at the [http://specs.openoffice.org/appwide/start_center/start_center.odt Specification Project].
* The development of the visual design has been documented on the pages of [http://ui.openoffice.org/VisualDesign/OOo_startup_dialog.html Visual Design].
* The StartCenter has been initially presented to the public at [http://blogs.sun.com/GullFOSS/entry/new_startcenter_replaces_startmodule GullFOSS].

== Discussion ==

Please note: The discussion has been started with the first version of the StartCenter (2008-02-19). Therefore not all of the given points may be valid at the moment.

What has been rated positively:

* The design appears very clear to the user.
* It welcomes the user “Say hello to iPo ... mmh ... OpenOffice.org” ;-)

What has been criticized so far:

* The spacing does not emphasize the functional representation of the elements.
* The "new from template" symbol is separated from the "new empty document" by the "open". Seems weird.
* The mouseover area is relatively small
* The three items in the lower right might need some explanation. People who use that window will probably need some extra guidance.
* There is no obvious way to get help (besides the main OOo start module).
* From the user's point of view it is not really required to show the product name and version number in such a prominent way.

== Constraints ==

The following constraints apply for the StartCenter for OpenOffice.org 3.0:

* The StartCenter must provide entries for the following OpenOffice.org modules (if installed):
** Writer (Text Document)
** Calc (Spreadsheet)
** Impress (Presentation)
** Draw (Drawing)
** Base (Database)
* The StartCenter must provide actions/links to:
** OpenOffice.org Help
** OpenOffice.org User Survey (Registration)
** OpenOffice.org Extensions Website
* The visual design is not part of the discussion, unless there are usability concerns.

== Known Design Issues ==
* In Impress, the “New Document” does not directly lead to an empty document. Instead it presents the the “Presentation Wizard”, which also allows to open an already available document.
* The “Template” button will open the window “Templates and Documents” which not correct.
* After creating or opening a document, the StartCenter disappears and the interaction with the user is done by the usual OpenOffice.org user interface elements.

= StartCenter for future versions of OpenOffice.org =

== The Central Features ==

=== Rationale ===

Whenever the user starts OpenOffice.org, he may plan to either:
* open an existing document
* create a new document (empty or from template)

Therefore, opening the desired existing document and creating a new one should be as fast and as easy to achieve as possible. For the most users, the optimal case would a single - straight forward - click to perform each task.

=== Historical Perspective ===

In a far away future, computers will be able to read the user's mind and automatically create a new document or locate the existing document that the user intends to open. Even if the user doesn't accurately remember the file name, this advanced computer will infer from existing incomplete data the correct document, therefore removing the need for this start center. But this is in a very far away future.

Traditionally, programs have focused on the documents use-history to predict which documents are likely to be re-used by the user. Recently-used ones are more likely to be accessed again, therefore programs have implemented features from '''full fledged document history''' to simple '''recent-document lists'''.

Although this algorithm works on average well, it sometimes fails. Especially with the raising creation of new content on the internet, the number of documents a user might access increases significantly, putting great strain on the limited ''recent-documents list''.

New concepts are therefore needed:
* easily track existing documents: if OOo cannot reliably guess which document the user intends to open, then ease manually finding this document; and
* increase the chance of a positive hit.

Various strategies will be discussed below, including automatic meta-data and tagging-features, as well as customising the history list (e.g. pinning documents in the history list - an approach followed by MS Office 2007).

== Collection of Ideas ==

The following list contains those ideas that could possibly useful for the user (alphabetical order). Please add your comments which may be helpful for the evaluation of the ideas.

{| class="prettytable"
| <center>'''Idea'''</center>
| <center>'''Details'''</center>
| <center>'''Comments'''</center>

|-
| Bug reporting
| It seems that many people hazzle with the OpenOffice.org Issue Tracker (if they have finally managed to find it).

It would be nice to implement basic bug description capabilities, similar to the ones implemented in the Document Recover feature ([http://specs.openoffice.org/appwide/recovery/Autorecovery.sxw Specification]).
|

|-
| Community content
| Provide access to community content like OpenOffice.org extensions, document templates, graphics or video tutorials.
|

|-
| Community information
| Give information on current community events or other news (e.g. RSS feeds for local activities).
|

|-
| Content management systems
| In the industry, content management systems are the preferred method to manage documents. Besides the file system integration, the StartCenter should provide extension capabilities to integrate with CMS.
|

|-
| Document recovery
| If OpenOffice.org has crashed, it usually saves the currently opened documents and provides “Document Recovery” after restarting the software.

Currently, the document recovery works very well but does not really fit into the UI design of OpenOffice.org. Additionally, it may interrupt the intended workflow ([http://specs.openoffice.org/appwide/errorreporter/error_report_2_0_ui_specification.odt Specification]).

(Example: After the crash of Calc, the user may not work on. The next day, he starts Writer and gets a request to decide on recovery. This blocks her/his intended workflow.)
|

|-
| Merge with splash screen
| The splash screen is a separate window and is displayed until the application has been loaded. There could be two approaches:

If the loading time could be reduced significantly, show the StartCenter as soon as possible without showing the splash screen.

- or -

If the loading time of OpenOffice.org could not be reduced, then merge the splash screen and the StartCenter (e.g. use the same window size, use some fading).
|

|-
| PIM Integration
| For OpenOffice.org 3.0 it is planned to provide PIM capabilities with Thunderbird an the extension Lightning. To improve the integration, the StartCenter could be provide basic information on mails, tasks and the schedule.
|

|-
| Recent documents
| For the StartCenter it is planned to create new documents or to open existing ones with the file selection dialog. Normally, users do work with a certain set of documents which could be implemented as recent or frequently used documents in the StartCenter.

Currently, access to recent documents is done in OpenOffice.org via the application “File” menu ([http://specs.openoffice.org/appwide/menus/FileMenu.sxw Specification]).
|

|-
| Replace start module
| Instead of showing the start module together with the StartCenter, the StartCenter could be extended to replace the start module completely.

Currently, the start module is the window that is shown if no special OpenOffice.org module is loaded ([http://specs.openoffice.org/appwide/start_module/StartModule.sxw Specification]).
|

|-
| Template management
| The document templates are currently managed at several places. The most important access to templates is given by the “Templates and Documents” window. This feature driven but non-charming window could be well integrated into the StartCenter.

Some time ago, there work has been started to improve the user experience. It seems that it has not been worked on for some time ([http://wiki.services.openoffice.org/wiki/Feature_-_Templates Feature Templates]).
|

|-
| Update information
| The StartCenter could provide information on online updates for the main product and extensions.

Currently, the user is informed about updates by a small icon in the upper right corner ([http://specs.openoffice.org/appwide/onlineupdate/Software_Update.odt Specification]).
|

|-
| User data
| The StartCenter could be used to acquire the personal data for the user. This data is generally used to fill out templates automatically or state the author in the change tracking feature.

Currently, most users don't see the need to fill out this form, do not know that it exists or don't trust OpenOffice.org.

The users could be encouraged to give their user data by using a “personal saluation” in the StartCenter.
|

|-
| User survey (Registration)
| The StartCenter could natively implement the user servery instead of providing it as a separate web page ([http://www.openoffice.org/welcome/registration20.html User Survey]).

In the current version of OpenOffice.org, the request for registration is prompted directly after installing the product (together with the licence agreement this harms the experience for the user). From that point, the registration option lives quiet in the help menu.
|

|-
| What's new?
| If an updated version is installed, the user may get a short introduction to new features.
It has been proposed to embed a web page into the StartCenter to add content like "New Features" information; please have a look at this [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2087 mail].

|

|-
| Lose the words 'Welcome to'
| They may be appropriate on first use after installation, but after that it is wrong to welcome someone to THEIR installation on THEIR computer to edit THEIR documents. The simple statement of the product name and version is all that is needed.
|

|-
| Integrated Message Panel
| A single small panel, providing enough room for one line of text, could be used as a dynamic communication medium that provides relevant and useful information in an unobtrusive way. Only one message would be displayed at a time. This could solve many of the above suggestions. A few examples:

* A welcome message on first run.
* Encouraging users to complete the user survey.
* Offering tips - this could be the default if no other relevant message is available(?)
* Document Recovery notices
* When a new version is released, the user is notified and a link is provided to both a What's New page and the download page.
|

|-
| Tabbed Interface
| Keeping the perils of feature bloat in mind, a tabbed interface could encourage use of the Start Center as a productivity boost. Options in the OOo Preferences could customize which tab is shown on startup, saving user's from constantly clicking to get to their most often used options. The tabs could be:

* New Document - similar to the current Start Center - offering one-click access to creating new documents & templates
* Open Document - a custom open-like dialog with 3 ways to open files:
** Recent Documents - a list of recent OOo documents, with information like filename, last modified, etc) with a 'pin' option to keep very frequently opened documents (as determined by the user) at the top of the list.
** Standard Open - allows the user to browse their hard disk and locate the file manually.
** Watched Directories - a possible new feature: users could specify directories to be 'watched' - OOo would then aggregate all OOo files from these directories and display them here - like a virtual directory.
* OOo Online - a window showing useful OOo links/information - extensions, clip art, templates, free support, news, etc.
* User Survey - a quick, convenient way of completing the user survey, resumable if the user doesn't want to do it all at once.
|

|-
| Desktop Search Integration
| Opening new documents or searching for previously used ones may be eased by desktop search integration. Here, users just enter search terms and start the query for the desired documents (search terms: file name, content, tags, ...). This may be even better than providing 10 ... 15 single entries of the last used documents.
Desktop search engines are for example: [http://www.apple.com/macosx/features/300.html#spotlight Apple Spotlight], [http://beagle-project.org/ Beagle], [http://www.gnome.org/projects/tracker/ Gnome Tracker], [http://desktop.google.com/ Google Desktop Search].
|

|-
| Customization via GUI
| The user should be able to customize the StartCenter via the GUI. Customization means, that the user would be able to define the content (e.g. community information, recent documents, update information) and its position in the StartCenter window to fit her/his personal needs. In any case, there should be well defined defaults.
(Added for the user jobod because of translation issues.)
|

|}

== Mockups ==

{| class="prettytable" border="1"

|-

! Name

! Mockup

! Details / Comments

|-

| Fancy Progressbar

| [[Image:StartCenter Idea ProgressBar Flare.png|375px]]

| If the StartCenter would be merged with the Splash Screen, then some people might fall in love with a more fancy progress bar. Flare effects and some slight animation might help to raise the enjoyment factor (animation: color changes of star, rotation, ...).

Please note:
* It would be even cooler if OpenOffice.org would start up lightning fast and therefore would not require to show a progress bar.
* The StartCenter window is just an example. Neither color, size, shape, ... nor background belong to that proposal.
* The picture was drawn by myself, which means that the idea may be better than my artistic skills ;-)

|-
| Possible New Start Center Mockup

| [[Image:Startcenter_mockup2.png|375px]]

| A Start Center integrating a message panel (please see relevant entry in the collection of ideas above) and recent documents. Please note: the header design is not indicative of OOo 3's final artwork (3 gulls artwork by Nikash Singh).

As a result of [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1793 presenting this to the mailing list], 2 main concerns were raised:

* The number of recent documents may not be sufficient. Displaying them would better be handled by the open dialog.
* The font sizes may be too small for visually impaired users.

This leads to the tabbed interface suggestion (please see relevant entry in the collection of ideas above)
|}

== How to continue? ==

At the moment, the “idea collection season” is open. So just add your brainstorming ideas on use cases, requirements, features and mockups. Then, those ideas should be evaluated in terms of “customer benefit”, “user types” and “effort”. After that we can finally start to design this feature and start implementing.

[[category:User Experience]]

User Experience/StartCenter

2008-12-27T07:40:36Z

Pgan002: /* Known Design Issues */

{{User Experience}}
= Introduction =

OpenOffice.org is separated into single applications like Writer, Calc, Draw and Impress, which could be started directly from the operating system start panel. If the OpenOffice.org executable is started directly OOo shows the start module, always shown if no document is loaded. The start module has no value for the user on start-up, but keeps OOo loaded if the last document has been closed and a new one is generated. The plain start module makes it difficult start OOo from a link on the desktop to gain visibility on the Macintosh platform.

So a new StartCenter is needed to welcome the user. The “welcome” implies that is very important for the experience of the user, because:

* ... it is the first element the user might see (besides the download and installation procedure).
* ... it is an essential part of OpenOffice.org's visual identity.
* ... it creates a first impression on the features and the usability of OpenOffice.org.
* ... it should encourage the new user to work with OpenOffice.org.

== Development ==
The development of the new StartCenter has begun and is open for community discussion. A first version of it will be part of OpenOffice.org 3.0. After that, this start center could be further extended from version to version. New ideas can be added in section Collection of Ideas.

== Terms and Definitions ==
The following graphics contains terms and definitions which might be helpful for the ongoing discussion.

[[Image:UX StartCenter Definitions.png|center]]

A discussion has been started if another name but "StartCenter" may make more sense. You find it at [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1295 ux-discuss Message 1295].

== Issues ==

* '''[http://www.openoffice.org/issues/buglist.cgi?email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=startcenter&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query Extended Issue List]''' with all entries having the description "StartCenter" independent of their status, priority, ...
* [http://www.openoffice.org/issues/show_bug.cgi?id=90815 Issue 90815] [StartCenter] Provide configuration option to deactivate StartCenter

= StartCenter for OpenOffice.org 3.0 =
This first step of the development, targeted for inclusion in OpenOffice.org 3.0, defines the integration into the operating system and a first welcome dialog within the former backing window.

* The specification for the StartCenter is located at the [http://specs.openoffice.org/appwide/start_center/start_center.odt Specification Project].
* The development of the visual design has been documented on the pages of [http://ui.openoffice.org/VisualDesign/OOo_startup_dialog.html Visual Design].
* The StartCenter has been initially presented to the public at [http://blogs.sun.com/GullFOSS/entry/new_startcenter_replaces_startmodule GullFOSS].

== Discussion ==

Please note: The discussion has been started with the first version of the StartCenter (2008-02-19). Therefore not all of the given points may be valid at the moment.

What has been rated positively:

* The design appears very clear to the user.
* It welcomes the user “Say hello to iPo ... mmh ... OpenOffice.org” ;-)

What has been criticized so far:

* The spacing does not emphasize the functional representation of the elements.
* The "new from template" symbol is separated from the "new empty document" by the "open". Seems weird.
* The mouseover area is relatively small
* The three items in the lower right might need some explanation. People who use that window will probably need some extra guidance.
* There is no obvious way to get help (besides the main OOo start module).
* From the user's point of view it is not really required to show the product name and version number in such a prominent way.

== Constraints ==

The following constraints apply for the StartCenter for OpenOffice.org 3.0:

* The StartCenter must provide entries for the following OpenOffice.org modules (if installed):
** Writer (Text Document)
** Calc (Spreadsheet)
** Impress (Presentation)
** Draw (Drawing)
** Base (Database)
* The StartCenter must provide actions/links to:
** OpenOffice.org Help
** OpenOffice.org User Survey (Registration)
** OpenOffice.org Extensions Website
* The visual design is not part of the discussion, unless there are usability concerns.

== Known Design Issues ==
* In Impress, the “New Document” does not directly lead to an empty document. Instead it presents the the “Presentation Wizard”, which also allows to open an already available document.
* The “Template” button will open the window “Templates and Documents” which not correct.
* After creating or opening a document, the StartCenter disappears and the interaction with the user is done by the usual OpenOffice.org user interface elements.

= StartCenter for future versions of OpenOffice.org =

== The Central Features ==

=== Rationale ===

Whenever the user starts OpenOffice.org, he may plan to either:
* open an existing document
* create a new document (empty or from template)

Therefore, opening the desired existing document and creating a new one should be as fast and as easy to achieve as possible. For the most users, the optimal case would a single - straight forward - click to perform each task.

=== Historical Perspective ===

In a far away future, computers will be able to read the user's mind and automatically create a new document or locate the existing document that the user intends to open. Even if the user doesn't accurately remember the file name, this advanced computer will infer from existing incomplete data the correct document, therefore removing the need for this start center. But this is in a very far away future.

Traditionally, programs have focused on the documents use-history to predict which documents are likely to be re-used by the user. Recently-used ones are more likely to be accessed again, therefore programs have implemented features from '''full fledged document history''' to simple '''recent-document lists'''.

Although this algorithm works on average well, it sometimes fails. Especially with the raising creation of new content on the internet, the number of documents a user might access increases significantly, putting great strain on the limited ''recent-documents list''.

New concepts are therefore needed:
* both to easily track existing documents: IF OOo cannot reliably guess which document the user intends to open than at least ease finding manually this one
* as well as increase the chance of a positive hit.

Various strategies will be discussed below, including automatic meta-data and tagging-features, as well as customising the history list (e.g. pinning documents in the history list - an approach followed by MS Office 2007).

== Collection of Ideas ==

The following list contains those ideas that could possibly useful for the user (alphabetical order). Please add your comments which may be helpful for the evaluation of the ideas.

{| class="prettytable"
| <center>'''Idea'''</center>
| <center>'''Details'''</center>
| <center>'''Comments'''</center>

|-
| Bug reporting
| It seems that many people hazzle with the OpenOffice.org Issue Tracker (if they have finally managed to find it).

It would be nice to implement basic bug description capabilities, similar to the ones implemented in the Document Recover feature ([http://specs.openoffice.org/appwide/recovery/Autorecovery.sxw Specification]).
|

|-
| Community content
| Provide access to community content like OpenOffice.org extensions, document templates, graphics or video tutorials.
|

|-
| Community information
| Give information on current community events or other news (e.g. RSS feeds for local activities).
|

|-
| Content management systems
| In the industry, content management systems are the preferred method to manage documents. Besides the file system integration, the StartCenter should provide extension capabilities to integrate with CMS.
|

|-
| Document recovery
| If OpenOffice.org has crashed, it usually saves the currently opened documents and provides “Document Recovery” after restarting the software.

Currently, the document recovery works very well but does not really fit into the UI design of OpenOffice.org. Additionally, it may interrupt the intended workflow ([http://specs.openoffice.org/appwide/errorreporter/error_report_2_0_ui_specification.odt Specification]).

(Example: After the crash of Calc, the user may not work on. The next day, he starts Writer and gets a request to decide on recovery. This blocks her/his intended workflow.)
|

|-
| Merge with splash screen
| The splash screen is a separate window and is displayed until the application has been loaded. There could be two approaches:

If the loading time could be reduced significantly, show the StartCenter as soon as possible without showing the splash screen.

- or -

If the loading time of OpenOffice.org could not be reduced, then merge the splash screen and the StartCenter (e.g. use the same window size, use some fading).
|

|-
| PIM Integration
| For OpenOffice.org 3.0 it is planned to provide PIM capabilities with Thunderbird an the extension Lightning. To improve the integration, the StartCenter could be provide basic information on mails, tasks and the schedule.
|

|-
| Recent documents
| For the StartCenter it is planned to create new documents or to open existing ones with the file selection dialog. Normally, users do work with a certain set of documents which could be implemented as recent or frequently used documents in the StartCenter.

Currently, access to recent documents is done in OpenOffice.org via the application “File” menu ([http://specs.openoffice.org/appwide/menus/FileMenu.sxw Specification]).
|

|-
| Replace start module
| Instead of showing the start module together with the StartCenter, the StartCenter could be extended to replace the start module completely.

Currently, the start module is the window that is shown if no special OpenOffice.org module is loaded ([http://specs.openoffice.org/appwide/start_module/StartModule.sxw Specification]).
|

|-
| Template management
| The document templates are currently managed at several places. The most important access to templates is given by the “Templates and Documents” window. This feature driven but non-charming window could be well integrated into the StartCenter.

Some time ago, there work has been started to improve the user experience. It seems that it has not been worked on for some time ([http://wiki.services.openoffice.org/wiki/Feature_-_Templates Feature Templates]).
|

|-
| Update information
| The StartCenter could provide information on online updates for the main product and extensions.

Currently, the user is informed about updates by a small icon in the upper right corner ([http://specs.openoffice.org/appwide/onlineupdate/Software_Update.odt Specification]).
|

|-
| User data
| The StartCenter could be used to acquire the personal data for the user. This data is generally used to fill out templates automatically or state the author in the change tracking feature.

Currently, most users don't see the need to fill out this form, do not know that it exists or don't trust OpenOffice.org.

The users could be encouraged to give their user data by using a “personal saluation” in the StartCenter.
|

|-
| User survey (Registration)
| The StartCenter could natively implement the user servery instead of providing it as a separate web page ([http://www.openoffice.org/welcome/registration20.html User Survey]).

In the current version of OpenOffice.org, the request for registration is prompted directly after installing the product (together with the licence agreement this harms the experience for the user). From that point, the registration option lives quiet in the help menu.
|

|-
| What's new?
| If an updated version is installed, the user may get a short introduction to new features.
It has been proposed to embed a web page into the StartCenter to add content like "New Features" information; please have a look at this [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2087 mail].

|

|-
| Lose the words 'Welcome to'
| They may be appropriate on first use after installation, but after that it is wrong to welcome someone to THEIR installation on THEIR computer to edit THEIR documents. The simple statement of the product name and version is all that is needed.
|

|-
| Integrated Message Panel
| A single small panel, providing enough room for one line of text, could be used as a dynamic communication medium that provides relevant and useful information in an unobtrusive way. Only one message would be displayed at a time. This could solve many of the above suggestions. A few examples:

* A welcome message on first run.
* Encouraging users to complete the user survey.
* Offering tips - this could be the default if no other relevant message is available(?)
* Document Recovery notices
* When a new version is released, the user is notified and a link is provided to both a What's New page and the download page.
|

|-
| Tabbed Interface
| Keeping the perils of feature bloat in mind, a tabbed interface could encourage use of the Start Center as a productivity boost. Options in the OOo Preferences could customize which tab is shown on startup, saving user's from constantly clicking to get to their most often used options. The tabs could be:

* New Document - similar to the current Start Center - offering one-click access to creating new documents & templates
* Open Document - a custom open-like dialog with 3 ways to open files:
** Recent Documents - a list of recent OOo documents, with information like filename, last modified, etc) with a 'pin' option to keep very frequently opened documents (as determined by the user) at the top of the list.
** Standard Open - allows the user to browse their hard disk and locate the file manually.
** Watched Directories - a possible new feature: users could specify directories to be 'watched' - OOo would then aggregate all OOo files from these directories and display them here - like a virtual directory.
* OOo Online - a window showing useful OOo links/information - extensions, clip art, templates, free support, news, etc.
* User Survey - a quick, convenient way of completing the user survey, resumable if the user doesn't want to do it all at once.
|

|-
| Desktop Search Integration
| Opening new documents or searching for previously used ones may be eased by desktop search integration. Here, users just enter search terms and start the query for the desired documents (search terms: file name, content, tags, ...). This may be even better than providing 10 ... 15 single entries of the last used documents.
Desktop search engines are for example: [http://www.apple.com/macosx/features/300.html#spotlight Apple Spotlight], [http://beagle-project.org/ Beagle], [http://www.gnome.org/projects/tracker/ Gnome Tracker], [http://desktop.google.com/ Google Desktop Search].
|

|-
| Customization via GUI
| The user should be able to customize the StartCenter via the GUI. Customization means, that the user would be able to define the content (e.g. community information, recent documents, update information) and its position in the StartCenter window to fit her/his personal needs. In any case, there should be well defined defaults.
(Added for the user jobod because of translation issues.)
|

|}

== Mockups ==

{| class="prettytable" border="1"

|-

! Name

! Mockup

! Details / Comments

|-

| Fancy Progressbar

| [[Image:StartCenter Idea ProgressBar Flare.png|375px]]

| If the StartCenter would be merged with the Splash Screen, then some people might fall in love with a more fancy progress bar. Flare effects and some slight animation might help to raise the enjoyment factor (animation: color changes of star, rotation, ...).

Please note:
* It would be even cooler if OpenOffice.org would start up lightning fast and therefore would not require to show a progress bar.
* The StartCenter window is just an example. Neither color, size, shape, ... nor background belong to that proposal.
* The picture was drawn by myself, which means that the idea may be better than my artistic skills ;-)

|-
| Possible New Start Center Mockup

| [[Image:Startcenter_mockup2.png|375px]]

| A Start Center integrating a message panel (please see relevant entry in the collection of ideas above) and recent documents. Please note: the header design is not indicative of OOo 3's final artwork (3 gulls artwork by Nikash Singh).

As a result of [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1793 presenting this to the mailing list], 2 main concerns were raised:

* The number of recent documents may not be sufficient. Displaying them would better be handled by the open dialog.
* The font sizes may be too small for visually impaired users.

This leads to the tabbed interface suggestion (please see relevant entry in the collection of ideas above)
|}

== How to continue? ==

At the moment, the “idea collection season” is open. So just add your brainstorming ideas on use cases, requirements, features and mockups. Then, those ideas should be evaluated in terms of “customer benefit”, “user types” and “effort”. After that we can finally start to design this feature and start implementing.

[[category:User Experience]]

User Experience/Command search

2008-12-04T06:51:45Z

Pgan002: /* Other details */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words.

The command box should appear next to the menu bar, right-aligned. It should contain the label "Type what you want to do (F7)" in faint color. The label disappears when the box is focused. A tool tip appears on mouse over, saying "Type in the box to invoke a command, e.g. 'insert table'".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, e.g. 'insert table'". Jim starts typing "insert table" and sees a list of commands, appear. Thus he understands what the box is for. When he needs to add a formula inside Writer, he focuses the command box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Command box placement ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Apart from their canonical name (e.g. "insert picture") commands may have synonym names ("add picture"). Synonyms can be created by hand, using the text in the Help, and a thesaurus. The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ordered alphabetically, by frecency, by relevance, or by date of addition.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
It may be useful to reveal the menu item for the selected command's (if there is a menu item), as in MacOS. But that would be too slow, distracting and would not encourage the user to use the command. Instead, we can highlight the enclosing menu in the menu bar (and the rest of the path path to the item) without; the user can open the menus if she is interested. Alternatively, each result that corresponds to a menu item can have an icon at the right edge, that when clicked opens the menu to reveal the item.

This command facility will not be included in the MacOSX version of OOo, at least initially, until it is better than the system search for menu items under the Help menu.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* MacOS X applications have a command box in the Help menu.
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far, but the code may be useful for implementing this current proposal.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font and right-aligned box
* Create a mock-up of the unfocused command box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command name for each menu item and button
* Add synonymous names where required
* Convert this document into a specification
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search/Commands

2008-12-04T06:12:50Z

Pgan002: /* Main menu entries */

This page is for designing the names of commands and their synonyms. The items are shown as they appear in menu entries and button tool tips, followed by additional or replacement command names for each.

Items are listed only once: that is, if an item is listed as a menu entry, it should not be listed again as a button, and if it is listed as a button in one tool bar, it should not be listed in another tool bar. Button tool bars are shown in order of approximate importance.

== Main menu entries ==
{| class="prettytable" border="1"
! Menu entry
! Command name
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Spreadsheet
| Create a new OpenOffice spreadsheet
|-
| File New Presentation
| Create a new presentation
|-
| File New Drawing
| Create a new drawing
|-
| File New HTML document
| Create a new HTML document
|-
| File New XML form document
| Create a new XML document
|-
| File New Master document
| Create a new master document
|-
| File New Labels
|-
| File New Business cards
|-
| File New Templates and documents
|-
| File Open...
| Open a document file...
|-
| File Recent documents
| (There will be one command for each recent document, called "Recent document XXX" where XXX is the name of the file.)
|-
| File Wizards Letter...
| Write a new Letter (wizard)...
|-
| File Wizards Fax...
| Write a new Fax (wizard)...
|-
| File Wizards Agenda...
| Write a new Agenda (wizard)...
|-
| File Wizards Presentation...
| Create a new Presentation (wizard)...
|-
| File Wizards Web page...
| Create a new Web page (wizard)...
|-
| File Wizards Document converter...
| Convert a document format...
|-
| File Wizards Euro converter...
| Convert money amounts to Euro currency...
|-
| File Wizards Install new dictionaries...
| Install a new dictionary...
|-
| File Close
| Close the current file
|-
| File Save
| Save the current file
|-
| File Save As...
| Save current file as ...
|-
| File Reload
| Reload the current file
|-
| File Versions...
| Manager the versions of the current document...
|-
| File Export...
| Export the current document...
|-
| File Export as PDF
| Export the current document as PDF
|-
| File Send Document as e-mail
| Send the current document as e-mail...
|-
| File Send E-mail as OpenDocument text...
|-
| File Send E-mail as Microsoft Word...
|-
| File Send E-mail as PDF...
|-
| File Send Create master document
|-
| File Send Create HTML document
|-
| File Send Outline to presentation
|-
| File Send Outline to Clipboard
|-
| File Send Create autoAbstract...
|-
| File Send AutoAbstract to presentation...
|-
| File Properties...
|-
| File Digital signatures...
|-
| File Templates Organize...
|-
| File Templates Save...
|-
| File Templates Edit...
|-
| File Preview in Web browser
|-
| File Page preview
| Preview how your document will look when it is printed
|-
| File Print...
| Print the current file...
|-
| File Printer settings...
| Set up a printer...
|-
| File exit
|-
| Edit (Can't) Undo (menu showing changes)
| Undo (1) typing "Hello there! How are you?" / Undo (2) typing "Hello"
|-
| Edit (Can't) Redo (menu showing changes)
| Redo (1) typing "Bye now see you later!" / Undo (2) typing "Bye"
|-
| Edit (Can't) Repeat (action)
| Repeat the last action
|-
| Edit Cut
| Cut the selected {text/table/image/formula/object/...} to the clipboard
|-
| Edit Copy
| Copy the selected {text/table/image/formula/object/...} to the clipboard
|-
| Edit Paste
| Past the {text/table/image/formula/object/...} from the clipboard
|-
| Edit Paste special...
|-
| Edit Selection mode Standard
| Use standard selection mode (rather than block area)
|-
| Edit Selection mode Block area
| Use block area selection mode
|-
| Edit Select all
| Select all (whole document)
|-
| Edit Changes Record (toggle)
| Record changes / Stop recording changes
|-
| Edit Changes Protect records...
| Protect records of changes...
|-
| Edit Changes Show (toggle)
| Show changes / Hide changes
|-
| Edit Changes Accept or reject...
| Accept or reject changes...
|-
| Edit Changes Comment...
|-
| Edit Changes Merge document...
|-
| Edit Compare document...
| Compare the current document to another document
|-
| Edit Find & replace...
| Find and replace text...
|-
| Edit Navigator
|-
| Edit AutoText...
|-
| Edit Exchange database
|-
| Edit Fields...
|-
| Edit Footnote...
|-
| Edit Index entry...
|-
| Edit Bibliography entry...
|-
| Edit Hyperlink
|-
| Edit Links...
|-
| Edit Plug-in
|-
| Edit Image map
|-
| Edit Object ???
|-
| View Print layout (alt1)
| View document in print layout
|-
| View Web layout (alt2)
| View document in Web layout
|-
| View Toolbars 3D-settings (toggle)
| {View/Hide} the 3D-settings tool bar
|-
| View Toolbars Align (toggle)
| {View/Hide} the Align tool bar
|-
| View Toolbars Bullets and numbering (toggle)
| {View/Hide} the Bullets and Numbering tool bar
|-
| View Toolbars Drawing (toggle)
| {View/Hide} the Drawing tool bar
|-
| View Toolbars Drawing object properties (toggle)
| {View/Hide} the Drawing Object Properties tool bar
|-
| View Toolbars Font work (toggle)
| {View/Hide} the Font Work tool bar
|-
| View Toolbars Form controls (toggle)
| {View/Hide} the Form Controls tool bar
|-
| View Toolbars Form design (toggle)
| {View/Hide} the Form Design tool bar
|-
| View Toolbars Form navigation (toggle)
| {View/Hide} the Form Navigation tool bar
|-
| View Toolbars Formatting (toggle)
| {View/Hide} the Formatting tool bar
|-
| View Toolbars Frame (toggle)
| {View/Hide} the Frame tool bar
|-
| View Toolbars Insert (toggle)
| {View/Hide} the Insert tool bar
|-
| View Toolbars Media playback (toggle)
| {View/Hide} the Media Playback tool bar
|-
| View Toolbars OLE-Object (toggle)
| {View/Hide} the OLE-Object tool bar
|-
| View Toolbars Picture (toggle)
| {View/Hide} the Picture tool bar
|-
| View Toolbars Standard (toggle)
| {View/Hide} the Standard tool bar
|-
| View Toolbars Standard (viewing mode) (toggle)
|-
| View Toolbars Table (toggle)
| {View/Hide} the Table tool bar
|-
| View Toolbars Table object (toggle)
| {View/Hide} the Table Object tool bar
|-
| View Toolbars Text object (toggle)
| {View/Hide} the Text Object
|-
| View Toolbars Tools (toggle)
| {View/Hide} the Tools tool bar
|-
| View Toolbars Hyperlink bar (toggle)
| {View/Hide} the Hyperlink tool bar
|-
| View Toolbars Formula (toggle)
| {View/Hide} the Formula tool bar
|-
| View Toolbars Customize... (toggle)
| Customize the tool bars...
|-
| View Toolbars Reset (toggle)
|-
| View Status bar (toggle)
| {View/Hide} the status bar
|-
| View Input methods status (toggle)
| {View/Hide} the Input Methods status
|-
| View Ruler (toggle)
| {View/Hide} the ruler
|-
| View Text boundaries (toggle)
| {View/Hide} the text boundaries
|-
| View Field shadings (toggle)
| {View/Hide} the field shadings
|-
| View Nonprinting Characters (toggle)
| {View/Hide} non-printing characters
|-
| View Hidden paragraphs (toggle)
| {View/Hide} hidden paragraphs
|-
| View Full screen
| View the document full screen
|-
| View Zoom...
| Change the zoom...
|-
| Insert Manual break...
| Insert a manual break...
|-
| Insert Fields Date
| Insert a date field
|-
| Insert Fields Time
| Insert a time field
|-
| Insert Fields Page number
| Insert a field showing the current page number
|-
| Insert Fields Page count
| Insert a page-count field
|-
| Insert Fields Subject
|-
| Insert Fields Title
|-
| Insert Fields Author
| Insert an Author field
|-
| Insert Fields Other...
| Insert other fields...
|-
| Insert Special character... (param: character name)
| Insert special character...
|-
| Insert Formatting mark Non-breaking space
| Insert a non-breaking space
|-
| Insert Formatting mark Non-breaking hyphen
| Insert a non-breaking hyphen
|-
| Insert formatting mark Optional hyphen
| Insert an optional hyphen
|-
| Insert Section... (param: number of columns; menu to select visually)
| Insert a section...
|-
| Insert Hyperlink
| Insert a hyperlink
|-
| Insert Header Default (toggle)
|-
| Insert Footer Default (toggle)
|-
| Insert Footnote...
| Insert a footnote...
|-
| Insert Caption...
| Insert a caption...
|-
| Insert Bookmark...
| Insert a bookmark...
|-
| Insert Cross-reference...
| Insert a cross-reference...
|-
| Insert Note...
| Insert a note (a comment)...
|-
| Insert Script...
| Insert a script...
|-
| Insert Indexes and tables Entry...
|-
| Insert Indexes and tables Indexes and tables...
|-
| Insert Indexes and tables Bibliographic entry...
|-
| Insert Envelope...
|-
| Insert Frame... (param: number of columns)
|-
| Insert Table... (param: number of rows "x" number of columns; selection menu)
|-
| Insert Horizontal ruler...
|-
| Insert Picture From file... (param: file name)
| Insert a picture from file...
|-
| Insert Picture Scan Select source...
| Scan a picture...
|-
| Insert Picture Scan Request...
|-
| Insert Movie and sound... (param: file name)
| Insert a movie or sound from file...
|-
| Insert Object OLE object...
| Insert an OLE object
|-
| Insert Object Plug-in...
| Insert a plug-in
|-
| Insert Object Sound...
|-
| Insert Object Video...
|-
| Insert Object Applet...
|-
| Insert Object Formula
|-
| Insert Object Chart...
|-
| Insert Floating frame
|-
| Insert File...
|-
| Format Default formatting
| Change to default formatting
|-
| Format Character...
| Character formatting...
|-
| Format Paragraph...
| Paragraph formatting...
|-
| Format Bullets and numbering...
| Format bullets and numbering...
|-
| Format Page...
| Page formatting...
|-
| Format Change case Uppercase
| Upper case the selected text
|-
| Format Change case Lowercase
| Lowercase the selected text
|-
| Format Columns...
| Column formatting
|-
| Format Sections...
| Section formatting
|-
| Format Styles and formatting
| Styles and formatting...
|-
| Format AutoFormat While typing (toggle)
| Auto-format while typing {on/off}
|-
| Format AutoFormat Apply
| Apply auto-format
|-
| Format AutoFormat Apply and edit changes
|-
| Format Anchor To page (alt1)
| Anchor the object to the page
|-
| Format Anchor To Paragraph (alt2)
| Anchor the object to the paragraph
|-
| Format Anchor To Character (alt3)
| Anchor the object to a character
|-
| Format Anchor As Character (alt4)
| Anchor the object as a character
|-
| Format Anchor To Frame (alt5)
| Anchor the object to the frame
|-
| Format Wrap Wrap off (alt1)
| Wrapping off
|-
| Format Wrap Page wrap (alt2)
| Wrap text to the page
|-
| Format Wrap Optimal page wrap (alt3)
| Wrap text optimally
|-
| Format Wrap Wrap through (alt4)
| Wrap through the object
|-
| Format Wrap In background (alt5)
| Wrap in the background
|-
| Format Wrap Contour (alt6)
|-
| Format Wrap Edit contour...
|-
| Format Wrap First paragraph (alt7)
|-
| Format Wrap Edit...
|-
| Format Alignment Left (alt1)
| Align left
|-
| Format Alignment Centered (alt2)
| Align centered
|-
| Format Alignment Right (alt3)
| Align right
|-
| Format Alignment Justified (alt4)
| Align justified
|-
| Format Arrange Bring to front
| Bring to the front
|-
| Format Arrange Bring Forward
| Bring forward
|-
| Format Arrange Send Backward
| Send backward
|-
| Format Arrange Send to Back
| Send to the back
|-
| Format Arrange To foreground
| Bring to the foreground
|-
| Format Arrange To background
| Send to the background
|-
| Format Flip Flip vertically
| Flip vertically
|-
| Format Flip Flip horizontally
| Flip horizontally
|-
| Format Group Group
| Group the objects together
|-
| Format Group Ungroup
| Ungroup the group of objects
|-
| Format Group Enter group
| Enter the selected group to manipulate the objects in it
|-
| Format Group Exit group
| Exit the entered group
|-
| Format Object Position and size...
| Format the object's position and size...
|-
| Format Object Line...
|-
| Format Object Area...
|-
| Format Object Text attributes
|-
| Format Object Fontwork
|-
| Format Object Description...
|-
| Format Object Name...
|-
| Format Frame...
|-
| Format Picture...
|-
| Table Insert Table...
| Insert a new table...
|-
| Table Insert Rows...
| Insert rows in the table...
|-
| Table Insert Columns...
| Insert columns in the table...
|-
| Table Delete Table
| Delete the table
|-
| Table Delete Rows
| Delete rows from the table
|-
| Table Delete Columns
| Delete columns from the table
|-
| Table Select Table
|-
| Table Select Rows
|-
| Table Select Columns
|-
| Table Select Cells
|-
| Table Merge cells
|-
| Table Split cells
|-
| Table Protect cells
|-
| Table Merge table
|-
| Table Split table
|-
| Table AutoFormat...
|-
| Table Autofit Column width...
|-
| Table Autofit Optimal column width
|-
| Table Autofit Distribute columns evenly
|-
| Table Autofit Row height...
|-
| Table Autofit Optimal row height
|-
| Table Autofit Distribute rows equally
|-
| Table Autofit Allow row to break across pages and columns
|-
| Table Heading rows repeat
|-
| Table Convert Text to table...
|-
| Table Convert Table to text...
|-
| Table Sort...
|-
| Table Formula
|-
| Table Number format...
|-
| Table Table boundaries (toggle)
|-
| Table Table properties...
|-
| Tools Spellcheck...
|-
| Tools Language For selection English (USA) (alt1)
|-
| Tools Language For selection Swedish (Sweden) (alt2)
|-
| Tools Language For selection None (do not check spelling) (alt3)
|-
| Tools Language For selection More...
|-
| Tools Language For paragraph English (USA) (alt1)
|-
| Tools Language For paragraph Swedish (Sweden) (alt2)
|-
| Tools Language For paragraph None (do not check spelling) (alt3)
|-
| Tools Language For paragraph More...
|-
| Tools Language For all text English (USA) (alt1)
|-
| Tools Language For all text Swedish (Sweden) (alt2)
|-
| Tools Language For all text None (do not check spelling) (alt3)
|-
| Tools Language For all text More...
|-
| Tools Language Thesaurus...
|-
| Tools Language Hyphenation...
|-
| Tools Word count
|-
| Tools AutoCorrect...
|-
| Tools Online numbering...
|-
| Tools Line numbering...
|-
| Tools Footnotes...
|-
| Tools Gallery
|-
| Tools Media player
|-
| Tools Bibliography database
|-
| Tools Mail merge wizard...
|-
| Tools Sort...
|-
| Tools Calculate
|-
| Tools Update Update all
|-
| Tools Update Fields
|-
| Tools Update Links
|-
| Tools Update All charts
|-
| Tools Update Current index
|-
| Tools Update All indexes and tables
|-
| Tools Update Page formatting
|-
| Tools Macros Record macro
|-
| Tools Macros Run macro...
|-
| Tools Macros Organize macros OpenOffice.org Basic...
|-
| Tools Macros Organize macros Python...
|-
| Tools Macros Organize macros BeanShell...
|-
| Tools Macros Organize macros JavaScript...
|-
| Tools Macros Digital signature...
|-
| Tools Macros Organize dialogs...
|-
| Tools Extension manager...
|-
| Tools XML filter settings...
|-
| Tools Customize...
|-
| Tools Options...
|-
| Window New window
|-
| Window Close
|-
| Help OpenOffice.org help
|-
| Help What's this
|-
| Help Get help online...
|-
| Help Translate this applications...
|-
| Help Report a bug...
|-
| Help About OpenOffice.org
|}

== Tool bar buttons ==
Tool bars are sorted by approximate importance.

=== Text object propoerties ===
Font name...
Font size...
Bold
Italic (italicize)
Underline
Superscript (toggle) (show "Subscript on" or "Subscript off")
Subscript (toggle) (show "Superscript on" or "Superscript off")
Alignt left
Alignt right
Centered (align center)
Justified alignment

=== Formatting ===
Styles and formatting
Apply style
Line spacing: 1 (single spacing)
Line spacing: 1.5 (1.5 spacing)
Line spacing: 2 (double spacing)
Numbering on/off (toggle)
Bullets on/off (toggle)
Decrease indent
Increase indent
Font color...
Highlighting... (highlight, unhighlight)
Background colror...
Left-to-right
Right-to-left

=== Picture (image) ===
Insert image from file (get image from file; add image from file)
Filter...
Graphics mode...
Color
Transparency...
Flip horizontally
Flip vertically
Frame properties

=== Frame ===
Wrap off
Page wrap
Wrap through
Align left
Center horizontal
Align right
Align top
Align vertical center (center vertical)
Align bottom
Borders...
Line style...
Line color (color of the border)...
Background color ... (color menu; param: color)
Frame properties
Bring to front
Send to back
Change anchor...
Link frames
Unlink frames

=== Table ===
Insert table (see [[#Insert]]; param: number of rows, number of columns)
Line style...
Line color (of the border)...
Borders...
Background color...
Optimize...
Top
Center (vertical)
Bottom
AutoFormat (auto-format)
Table properties...
Sort
Sum

=== OLE-object ===
Apply style...
Align left
Align right
Align center horizontal
Align top
Align vertical
Align bottom
Wrap off
Page wrap
Wrap through
Frame properties
Bring to front
Send to back
Change anchor...
Borders...
Line style...
Border line color

=== Align ===
Left
Centered
Right
Top
Center [vertically]
Bottom

=== Fontwork ===
Fontwork gallery
Fontwork shape...
Fontwork same letter heights
Fontwork alignment...
Fontwork character spacing...

=== Formula ===
Formula text [text box]
Sum
Round
Percent
Square
Square root
Power
List separator
Equal
Not equal
Less than or equal
Greater than or equal
Less
Greater
Boolean Or
Boolean Xor
Boolean And
Boolean Not
Mean
Minimum
Maximum
Sine
Cosine
Tangent
Arcsine
Arccosine
Arctangent

=== Insert ===
Frame (param: number of columns)
AutoText [lots of options, not worth implementing]

=== Tools ===
Direct cursor on/off (toggle)
Hyphenation
Thesaurus
Graphics on/off (toggle)
Web layout/print layout (toggle)

=== Standard ===
Edit file (toggle)
AutoSpellcheck (auto-spellcheck, auto-spell-check)
Format paintbrush
Show draw functions (drawing tool bar)

=== Drawing ===
Select tool
Line
Freeform line
Text
Call-out
Points
Fontwork gallery
Image from file... (param: file name)
Extrusion on/off (toggle)

==== Shapes ====
Rectangle
Rectangle with rounded edges
Square
Square with rounded edges
Circle
Ellipse (oval)
Circle pie
Isosceles trianlge
Right triangle
Trapezoid (trapezium)
Diamond (rhombus)
Parallelogram
Regular pentagon
Regular hexagon
Regular octagon
Cross
Ring
Block-arc (rainbow, half-ring)
Cylinder
Cube
Folded corner
Frame

==== Symbol shapes ====
Smiley face (smiling face)
Sun
Moon
Lightning bolt
Heart
Flower
Cloud
"Prohibited" symbol
Puzzle
Double bracket
Left bracket
Right bracket
Double brace
Left brace
Right brace
Square bevel
Octagon bevel
Diamond bevel (rhombus bevel)

==== Block arrows ====
Left arrow
Right arrow
Up arrow
Down arrow
Left and right arrow (Double arrow horizontal)
Up and down arrow (Double arrow vertical)
Up and right arrow
Up, right and down arrow
4-way arrow (four-way arrow)
Corner right arrow
Split arrow
Striped right arrow
Notched right arrow
Pentagon
Chevron
Right arrow call-out
Left arrow call-out
Up arrow call-out
Down arrow call-out
Left and right arrow call-out
Up and down arrow call-out
Up and right arrow call-out
4-way arrow call-out (four-way arrow call-out)
Circular arrow
Right or left arrow
S-shaped arrow

==== Flowchart symbols ====
Process (square)
Alternative process (square with rounded corners)
Decision (rhombus, diamond)
Data (parallelogram)
Predefined process
Internal storage
Document
Multi-document
Terminator
Preparation (regular hexagon)
Manual input (vertical trapezium)
Manual operation (horizontal trapezium)
Connector (circle)
Off-page connector
Card
Punched tape
Summing junction
Or
Collate
Sort
Extract
Merge
Sorted data
Delay
Sequential access
Magnetic disc
Direct access storage
Display

==== Callouts (call-outs) ====
Rectangular call-out
Rounded rectangular call-out
Round call-out
Cloud call-out
Straight line call-out
Bent line call-out
Disconnected straight line call-out

==== Stars ====
Explosion
4-point star (four-point star)
5-point star (five-point star)
6-point star (six-point star, star of David)
8-point star (eight-point star)
12-point star (twelve-point star)
24-point star
6-point star, concave
Vertical scroll
Horizontal scroll
Signet
Doorplate

=== Form design ===
Select
Design mode on/off (toggle)
Control
Form
Form navigator
Add field
Activation order
Open in design mode
Automatic control focus
Position and size
Change anchor
Alignment (param: [[#Align]])
Display grid (show grid)
Snap to grid
Guides when moving (show guides when moving)

=== Form controls ===
Select
Design mode on/off (toggle)
Control
Form
Check box
Text box
Formatted fields
Push button
Option button
List box
Combo box
Label field
[[#Form design]]

==== More form controls ====
Spin button
Scroll bar
Image button
Image control
Date field
Time field
File selection
Numerical field
Currency field
Pattern field
Group box

=== Form navigation ===
Find record
Record
Absolute record
Text-record
Total no. of records (Total number of records)
First record
Previous record
Next record
Last record
New record
Save record
Undo: Data entry
Delete record
Refresh
Sort
Sort ascending
Sort descending
Auto filter
Apply filter
Form-based filters
Remove filter/sort
Data source as table

=== 3D settings ===
Extrusion on/off (toggle)
Tilt down
Tilt up
Tilt left
Tilt right
Depth...
Direction...
Lighting...
Surface...
3D color

=== Media playback ===
If any of the actions below are executed, the tool bar should appear.
Movie and sound
Play
Pause
Stop
Repeat
Mute
View ???

User Experience/Command search/Commands

2008-12-04T05:03:01Z

Pgan002: /* Main menu entries */

This page is for designing the names of commands and their synonyms. The items are shown as they appear in menu entries and button tool tips, followed by additional or replacement command names for each.

Items are listed only once: that is, if an item is listed as a menu entry, it should not be listed again as a button, and if it is listed as a button in one tool bar, it should not be listed in another tool bar. Button tool bars are shown in order of approximate importance.

== Main menu entries ==
{| class="prettytable" border="1"
! Menu entry
! Command name
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Spreadsheet
| Create a new OpenOffice spreadsheet
|-
| File New Presentation
| Create a new presentation
|-
| File New Drawing
| Create a new drawing
|-
| File New HTML document
| Create a new HTML document
|-
| File New XML form document
| Create a new XML document
|-
| File New Master document
| Create a new master document
|-
| File New Labels
|-
| File New Business cards
|-
| File New Templates and documents
|-
| File Open...
| Open document file
|-
| File Recent documents
|-
| File Wizards Letter...
|-
| File Wizards Fax...
|-
| File Wizards Agenda...
|-
| File Wizards Presentation...
|-
| File Wizards Web page...
|-
| File Wizards Document converter...
|-
| File Wizards Euro converter...
|-
| File Wizards Install new dictionaries...
|-
| File Close
| Close the current file
|-
| File Save
| Save the current file
|-
| File Save As...
| Save file as ...
|-
| File Reload
|-
| File Versions...
|-
| File Export...
|-
| File Export as PDF
|-
| File Send Document as e-mail
|-
| File Send E-mail as OpenDocument text...
|-
| File Send E-mail as Microsoft Word...
|-
| File Send E-mail as PDF...
|-
| File Send Create master document
|-
| File Send Create HTML document
|-
| File Send Outline to presentation
|-
| File Send Outline to Clipboard
|-
| File Send Create autoAbstract...
|-
| File Send AutoAbstract to presentation...
|-
| File Properties...
|-
| File Digital signatures...
|-
| File Templates Organize...
|-
| File Templates Save...
|-
| File Templates Edit...
|-
| File Preview in Web browser
|-
| File Page preview
|-
| File Print...
|-
| File Printer settings...
|-
| File exit
|-
| Edit (Can't) Undo (menu showing changes)
|-
| Edit (Can't) Redo (menu showing changes)
|-
| Edit (Can't) Repeat (action)
|-
| Edit Cut
|-
| Edit Copy
|-
| Edit Paste
|-
| Edit Paste special...
|-
| Edit Selection mode Standard
|-
| Edit Selection mode Block area
|-
| Edit Select all
|-
| Edit Changes Record (toggle)
|-
| Edit Changes Protect records...
|-
| Edit Changes Show (toggle)
|-
| Edit Changes Accept or reject...
|-
| Edit Changes Comment...
|-
| Edit Changes Merge document...
|-
| Edit Compare document...
|-
| Edit Find & replace...
|-
| Edit Navigator
|-
| Edit AutoText...
|-
| Edit Exchange database
|-
| Edit Fields...
|-
| Edit Footnote...
|-
| Edit Index entry...
|-
| Edit Bibliography entry...
|-
| Edit hyperlink
|-
| Edit Links...
|-
| Edit Plug-in
|-
| Edit Image map
|-
| Edit Object ???
|-
| View Print layout (alt1)
|-
| View Web layout (alt2)
|-
| View Toolbars 3D-settings (toggle)
|-
| View Toolbars Align (toggle)
|-
| View Toolbars Bullets and numbering (toggle)
|-
| View Toolbars Drawing (toggle)
|-
| View Toolbars Drawing object properties (toggle)
|-
| View Toolbars Font work (toggle)
|-
| View Toolbars Form controls (toggle)
|-
| View Toolbars Form design (toggle)
|-
| View Toolbars Form navigation (toggle)
|-
| View Toolbars Formatting (toggle)
|-
| View Toolbars Frame (toggle)
|-
| View Toolbars Insert (toggle)
|-
| View Toolbars Media playback (toggle)
|-
| View Toolbars OLE-Object (toggle)
|-
| View Toolbars Picture (toggle)
|-
| View Toolbars Standard (toggle)
|-
| View Toolbars Standard (viewing mode) (toggle)
|-
| View Toolbars Table (toggle)
|-
| View Toolbars Table object (toggle)
|-
| View Toolbars Text object (toggle)
|-
| View Toolbars Tools (toggle)
|-
| View Toolbars Hyperlink bar (toggle)
|-
| View Toolbars Formula (toggle)
|-
| View Toolbars Customize (toggle)
|-
| View Toolbars Reset (toggle)
|-
| View Status bar (toggle)
|-
| View Input methods status (toggle)
|-
| View Ruler (toggle)
|-
| View Text boundaries (toggle)
|-
| View Field shadings (toggle)
|-
| View Nonprinting Characters (toggle)
|-
| View Hidden paragraphs (toggle)
|-
| View Full screen
|-
| View Zoom...
|-
| Insert Manual break...
|-
| Insert Fields Date
|-
| Insert Fields Time
|-
| Insert Fields Page number
|-
| Insert Fields Page count
|-
| Insert Fields Subject
|-
| Insert Fields Title
|-
| Insert Fields Author
|-
| Insert Fields Other...
|-
| Insert Special character... (param: character name)
|-
| Insert Formatting mark Non-breaking space
|-
| Insert Formatting mark Non-breaking hyphen
|-
| Insert formatting mark Optional hyphen
|-
| Insert Section... (param: number of columns; menu to select visually)
|-
| Insert Hyperlink
|-
| Insert Header Default (toggle)
|-
| Insert Footer Default (toggle)
|-
| Insert Footnote...
|-
| Insert Caption...
|-
| Insert Bookmark...
|-
| Insert Cross-reference...
|-
| Insert Note...
|-
| Insert Script...
|-
| Insert Indexes and tables Entry...
|-
| Insert Indexes and tables Indexes and tables...
|-
| Insert Indexes and tables Bibliographic entry...
|-
| Insert Envelope...
|-
| Insert Frame... (param: number of columns)
|-
| Insert Table... (param: number of rows "x" number of columns; selection menu)
|-
| Insert Horizontal ruler...
|-
| Insert Picture From file... (param: file name)
|-
| Insert Picture Scan Select source...
|-
| Insert Picture Scan Request...
|-
| Insert Movie and sound... (param: file name)
|-
| Insert Object OLE object...
|-
| Insert Plug-in...
|-
| Insert Sound...
|-
| Insert Video...
|-
| Insert Applet...
|-
| Insert Formula
|-
| Insert Chart...
|-
| Insert Floating frame
|-
| Insert File...
|-
| Format Default formatting
|-
| Format Character...
|-
| Format Paragraph...
|-
| Format Bullets and numbering...
|-
| Format Page...
|-
| Format Change case Uppercase
|-
| Format Change case Lowercase
|-
| Format Columns...
|-
| Format Sections...
|-
| Format Styles and formatting
|-
| Format AutoFormat While typing (toggle)
|-
| Format AutoFormat Apply
|-
| Format AutoFormat Apply and edit changes
|-
| Format Anchor To page (alt1)
|-
| Format Anchor To Paragraph (alt2)
|-
| Format Anchor To Character (alt3)
|-
| Format Anchor As Character (alt4)
|-
| Format Anchor To Frame (alt5)
|-
| Format Wrap Wrap off (alt1)
|-
| Format Wrap Page wrap (alt2)
|-
| Format Wrap Optimal page wrap (alt3)
|-
| Format Wrap Wrap through (alt4)
|-
| Format Wrap In background (alt5)
|-
| Format Wrap Contour (alt6)
|-
| Format Wrap Edit contour...
|-
| Format Wrap First paragraph (alt7)
|-
| Format Wrap Edit...
|-
| Format Alignment Left (alt1)
|-
| Format Alignment Centered (alt2)
|-
| Format Alignment Right (alt3)
|-
| Format Alignment Justified (alt4)
|-
| Format Arrange Bring to front
|-
| Format Arrange Bring Forward
|-
| Format Arrange Send Backward
|-
| Format Arrange Send to Back
|-
| Format Arrange To foreground
|-
| Format Arrange To background
|-
| Format Flip Flip vertically
|-
| Format Flip Flip horizontally
|-
| Format Group Group
|-
| Format Group Ungroup
|-
| Format Group Enter group
|-
| Format Group Exit group
|-
| Format Object Position and size
|-
| Format Object Line...
|-
| Format Object Area...
|-
| Format Object Text attributes
|-
| Format Object Fontwork
|-
| Format Object Description...
|-
| Format Object Name...
|-
| Format Frame...
|-
| Format Picture...
|-
| Table Insert Table...
|-
| Table Insert Rows...
|-
| Table Insert Columns...
|-
| Table Delete Table
|-
| Table Delete Rows
|-
| Table Delete Columns
|-
| Table Select Table
|-
| Table Select Rows
|-
| Table Select Columns
|-
| Table Select Cells
|-
| Table Merge cells
|-
| Table Split cells
|-
| Table Protect cells
|-
| Table Merge table
|-
| Table Split table
|-
| Table AutoFormat...
|-
| Table Autofit Column width...
|-
| Table Autofit Optimal column width
|-
| Table Autofit Distribute columns evenly
|-
| Table Autofit Row height..
|-
| Table Autofit Optimal row height
|-
| Table Autofit Distribute rows equally
|-
| Table Autofit Allow row to break across pages and columns
|-
| Table Heading rows repeat
|-
| Table Convert Text to table...
|-
| Table Convert Table to text...
|-
| Table Sort...
|-
| Table Formula
|-
| Table Number format...
|-
| Table Table boundaries (toggle)
|-
| Table Table properties...
|-
| Tools Spellcheck...
|-
| Tools Language For selection English (USA) (alt1)
|-
| Tools Language For selection Swedish (Sweden) (alt2)
|-
| Tools Language For selection None (do not check spelling) (alt3)
|-
| Tools Language For selection More...
|-
| Tools Language For paragraph English (USA) (alt1)
|-
| Tools Language For paragraph Swedish (Sweden) (alt2)
|-
| Tools Language For paragraph None (do not check spelling) (alt3)
|-
| Tools Language For paragraph More...
|-
| Tools Language For all text English (USA) (alt1)
|-
| Tools Language For all text Swedish (Sweden) (alt2)
|-
| Tools Language For all text None (do not check spelling) (alt3)
|-
| Tools Language For all text More...
|-
| Tools Language Thesaurus...
|-
| Tools Language Hyphenation...
|-
| Tools Word count
|-
| Tools AutoCorrect...
|-
| Tools Online numbering...
|-
| Tools Line numbering...
|-
| Tools Footnotes...
|-
| Tools Gallery
|-
| Tools Media player
|-
| Tools Bibliography database
|-
| Tools Mail merge wizard...
|-
| Tools Sort...
|-
| Tools Calculate
|-
| Tools Update Update all
|-
| Tools Update Fields
|-
| Tools Update Links
|-
| Tools Update All charts
|-
| Tools Update Current index
|-
| Tools Update All indexes and tables
|-
| Tools Update Page formatting
|-
| Tools Macros Record macro
|-
| Tools Macros Run macro...
|-
| Tools Macros Organize macros OpenOffice.org Basic...
|-
| Tools Macros Organize macros Python...
|-
| Tools Macros Organize macros BeanShell...
|-
| Tools Macros Organize macros JavaScript...
|-
| Tools Macros Digital signature...
|-
| Tools Macros Organize dialogs...
|-
| Tools Extension manager...
|-
| Tools XML filter settings...
|-
| Tools Customize...
|-
| Tools Options...
|-
| Window New window
|-
| Window Close
|-
| Help OpenOffice.org help
|-
| Help What's this
|-
| Help Get help online...
|-
| Help Translate this applications...
|-
| Help Report a bug...
|-
| Help About OpenOffice.org
|}

== Tool bar buttons ==
Tool bars are sorted by approximate importance.

=== Text object propoerties ===
Font name...
Font size...
Bold
Italic (italicize)
Underline
Superscript (toggle) (show "Subscript on" or "Subscript off")
Subscript (toggle) (show "Superscript on" or "Superscript off")
Alignt left
Alignt right
Centered (align center)
Justified alignment

=== Formatting ===
Styles and formatting
Apply style
Line spacing: 1 (single spacing)
Line spacing: 1.5 (1.5 spacing)
Line spacing: 2 (double spacing)
Numbering on/off (toggle)
Bullets on/off (toggle)
Decrease indent
Increase indent
Font color...
Highlighting... (highlight, unhighlight)
Background colror...
Left-to-right
Right-to-left

=== Picture (image) ===
Insert image from file (get image from file; add image from file)
Filter...
Graphics mode...
Color
Transparency...
Flip horizontally
Flip vertically
Frame properties

=== Frame ===
Wrap off
Page wrap
Wrap through
Align left
Center horizontal
Align right
Align top
Align vertical center (center vertical)
Align bottom
Borders...
Line style...
Line color (color of the border)...
Background color ... (color menu; param: color)
Frame properties
Bring to front
Send to back
Change anchor...
Link frames
Unlink frames

=== Table ===
Insert table (see [[#Insert]]; param: number of rows, number of columns)
Line style...
Line color (of the border)...
Borders...
Background color...
Optimize...
Top
Center (vertical)
Bottom
AutoFormat (auto-format)
Table properties...
Sort
Sum

=== OLE-object ===
Apply style...
Align left
Align right
Align center horizontal
Align top
Align vertical
Align bottom
Wrap off
Page wrap
Wrap through
Frame properties
Bring to front
Send to back
Change anchor...
Borders...
Line style...
Border line color

=== Align ===
Left
Centered
Right
Top
Center [vertically]
Bottom

=== Fontwork ===
Fontwork gallery
Fontwork shape...
Fontwork same letter heights
Fontwork alignment...
Fontwork character spacing...

=== Formula ===
Formula text [text box]
Sum
Round
Percent
Square
Square root
Power
List separator
Equal
Not equal
Less than or equal
Greater than or equal
Less
Greater
Boolean Or
Boolean Xor
Boolean And
Boolean Not
Mean
Minimum
Maximum
Sine
Cosine
Tangent
Arcsine
Arccosine
Arctangent

=== Insert ===
Frame (param: number of columns)
AutoText [lots of options, not worth implementing]

=== Tools ===
Direct cursor on/off (toggle)
Hyphenation
Thesaurus
Graphics on/off (toggle)
Web layout/print layout (toggle)

=== Standard ===
Edit file (toggle)
AutoSpellcheck (auto-spellcheck, auto-spell-check)
Format paintbrush
Show draw functions (drawing tool bar)

=== Drawing ===
Select tool
Line
Freeform line
Text
Call-out
Points
Fontwork gallery
Image from file... (param: file name)
Extrusion on/off (toggle)

==== Shapes ====
Rectangle
Rectangle with rounded edges
Square
Square with rounded edges
Circle
Ellipse (oval)
Circle pie
Isosceles trianlge
Right triangle
Trapezoid (trapezium)
Diamond (rhombus)
Parallelogram
Regular pentagon
Regular hexagon
Regular octagon
Cross
Ring
Block-arc (rainbow, half-ring)
Cylinder
Cube
Folded corner
Frame

==== Symbol shapes ====
Smiley face (smiling face)
Sun
Moon
Lightning bolt
Heart
Flower
Cloud
"Prohibited" symbol
Puzzle
Double bracket
Left bracket
Right bracket
Double brace
Left brace
Right brace
Square bevel
Octagon bevel
Diamond bevel (rhombus bevel)

==== Block arrows ====
Left arrow
Right arrow
Up arrow
Down arrow
Left and right arrow (Double arrow horizontal)
Up and down arrow (Double arrow vertical)
Up and right arrow
Up, right and down arrow
4-way arrow (four-way arrow)
Corner right arrow
Split arrow
Striped right arrow
Notched right arrow
Pentagon
Chevron
Right arrow call-out
Left arrow call-out
Up arrow call-out
Down arrow call-out
Left and right arrow call-out
Up and down arrow call-out
Up and right arrow call-out
4-way arrow call-out (four-way arrow call-out)
Circular arrow
Right or left arrow
S-shaped arrow

==== Flowchart symbols ====
Process (square)
Alternative process (square with rounded corners)
Decision (rhombus, diamond)
Data (parallelogram)
Predefined process
Internal storage
Document
Multi-document
Terminator
Preparation (regular hexagon)
Manual input (vertical trapezium)
Manual operation (horizontal trapezium)
Connector (circle)
Off-page connector
Card
Punched tape
Summing junction
Or
Collate
Sort
Extract
Merge
Sorted data
Delay
Sequential access
Magnetic disc
Direct access storage
Display

==== Callouts (call-outs) ====
Rectangular call-out
Rounded rectangular call-out
Round call-out
Cloud call-out
Straight line call-out
Bent line call-out
Disconnected straight line call-out

==== Stars ====
Explosion
4-point star (four-point star)
5-point star (five-point star)
6-point star (six-point star, star of David)
8-point star (eight-point star)
12-point star (twelve-point star)
24-point star
6-point star, concave
Vertical scroll
Horizontal scroll
Signet
Doorplate

=== Form design ===
Select
Design mode on/off (toggle)
Control
Form
Form navigator
Add field
Activation order
Open in design mode
Automatic control focus
Position and size
Change anchor
Alignment (param: [[#Align]])
Display grid (show grid)
Snap to grid
Guides when moving (show guides when moving)

=== Form controls ===
Select
Design mode on/off (toggle)
Control
Form
Check box
Text box
Formatted fields
Push button
Option button
List box
Combo box
Label field
[[#Form design]]

==== More form controls ====
Spin button
Scroll bar
Image button
Image control
Date field
Time field
File selection
Numerical field
Currency field
Pattern field
Group box

=== Form navigation ===
Find record
Record
Absolute record
Text-record
Total no. of records (Total number of records)
First record
Previous record
Next record
Last record
New record
Save record
Undo: Data entry
Delete record
Refresh
Sort
Sort ascending
Sort descending
Auto filter
Apply filter
Form-based filters
Remove filter/sort
Data source as table

=== 3D settings ===
Extrusion on/off (toggle)
Tilt down
Tilt up
Tilt left
Tilt right
Depth...
Direction...
Lighting...
Surface...
3D color

=== Media playback ===
If any of the actions below are executed, the tool bar should appear.
Movie and sound
Play
Pause
Stop
Repeat
Mute
View ???

User Experience/Command search/Commands

2008-12-04T05:01:57Z

Pgan002: /* Main menu entries */

This page is for designing the names of commands and their synonyms. The items are shown as they appear in menu entries and button tool tips, followed by additional or replacement command names for each.

Items are listed only once: that is, if an item is listed as a menu entry, it should not be listed again as a button, and if it is listed as a button in one tool bar, it should not be listed in another tool bar. Button tool bars are shown in order of approximate importance.

== Main menu entries ==
{| class="table" border=1 
! Menu entry
! Command name
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Spreadsheet
| Create a new OpenOffice spreadsheet
|-
| File New Presentation
| Create a new presentation
|-
| File New Drawing
| Create a new drawing
|-
| File New HTML document
| Create a new HTML document
|-
| File New XML form document
| Create a new XML document
|-
| File New Master document
| Create a new master document
|-
| File New Labels
|-
| File New Business cards
|-
| File New Templates and documents
|-
| File Open...
| Open document file
|-
| File Recent documents
|-
| File Wizards Letter...
|-
| File Wizards Fax...
|-
| File Wizards Agenda...
|-
| File Wizards Presentation...
|-
| File Wizards Web page...
|-
| File Wizards Document converter...
|-
| File Wizards Euro converter...
|-
| File Wizards Install new dictionaries...
|-
| File Close
| Close the current file
|-
| File Save
| Save the current file
|-
| File Save As...
| Save file as ...
|-
| File Reload
|-
| File Versions...
|-
| File Export...
|-
| File Export as PDF
|-
| File Send Document as e-mail
|-
| File Send E-mail as OpenDocument text...
|-
| File Send E-mail as Microsoft Word...
|-
| File Send E-mail as PDF...
|-
| File Send Create master document
|-
| File Send Create HTML document
|-
| File Send Outline to presentation
|-
| File Send Outline to Clipboard
|-
| File Send Create autoAbstract...
|-
| File Send AutoAbstract to presentation...
|-
| File Properties...
|-
| File Digital signatures...
|-
| File Templates Organize...
|-
| File Templates Save...
|-
| File Templates Edit...
|-
| File Preview in Web browser
|-
| File Page preview
|-
| File Print...
|-
| File Printer settings...
|-
| File exit
|-
| Edit (Can't) Undo (menu showing changes)
|-
| Edit (Can't) Redo (menu showing changes)
|-
| Edit (Can't) Repeat (action)
|-
| Edit Cut
|-
| Edit Copy
|-
| Edit Paste
|-
| Edit Paste special...
|-
| Edit Selection mode Standard
|-
| Edit Selection mode Block area
|-
| Edit Select all
|-
| Edit Changes Record (toggle)
|-
| Edit Changes Protect records...
|-
| Edit Changes Show (toggle)
|-
| Edit Changes Accept or reject...
|-
| Edit Changes Comment...
|-
| Edit Changes Merge document...
|-
| Edit Compare document...
|-
| Edit Find & replace...
|-
| Edit Navigator
|-
| Edit AutoText...
|-
| Edit Exchange database
|-
| Edit Fields...
|-
| Edit Footnote...
|-
| Edit Index entry...
|-
| Edit Bibliography entry...
|-
| Edit hyperlink
|-
| Edit Links...
|-
| Edit Plug-in
|-
| Edit Image map
|-
| Edit Object ???
|-
| View Print layout (alt1)
|-
| View Web layout (alt2)
|-
| View Toolbars 3D-settings (toggle)
|-
| View Toolbars Align (toggle)
|-
| View Toolbars Bullets and numbering (toggle)
|-
| View Toolbars Drawing (toggle)
|-
| View Toolbars Drawing object properties (toggle)
|-
| View Toolbars Font work (toggle)
|-
| View Toolbars Form controls (toggle)
|-
| View Toolbars Form design (toggle)
|-
| View Toolbars Form navigation (toggle)
|-
| View Toolbars Formatting (toggle)
|-
| View Toolbars Frame (toggle)
|-
| View Toolbars Insert (toggle)
|-
| View Toolbars Media playback (toggle)
|-
| View Toolbars OLE-Object (toggle)
|-
| View Toolbars Picture (toggle)
|-
| View Toolbars Standard (toggle)
|-
| View Toolbars Standard (viewing mode) (toggle)
|-
| View Toolbars Table (toggle)
|-
| View Toolbars Table object (toggle)
|-
| View Toolbars Text object (toggle)
|-
| View Toolbars Tools (toggle)
|-
| View Toolbars Hyperlink bar (toggle)
|-
| View Toolbars Formula (toggle)
|-
| View Toolbars Customize (toggle)
|-
| View Toolbars Reset (toggle)
|-
| View Status bar (toggle)
|-
| View Input methods status (toggle)
|-
| View Ruler (toggle)
|-
| View Text boundaries (toggle)
|-
| View Field shadings (toggle)
|-
| View Nonprinting Characters (toggle)
|-
| View Hidden paragraphs (toggle)
|-
| View Full screen
|-
| View Zoom...
|-
| Insert Manual break...
|-
| Insert Fields Date
|-
| Insert Fields Time
|-
| Insert Fields Page number
|-
| Insert Fields Page count
|-
| Insert Fields Subject
|-
| Insert Fields Title
|-
| Insert Fields Author
|-
| Insert Fields Other...
|-
| Insert Special character... (param: character name)
|-
| Insert Formatting mark Non-breaking space
|-
| Insert Formatting mark Non-breaking hyphen
|-
| Insert formatting mark Optional hyphen
|-
| Insert Section... (param: number of columns; menu to select visually)
|-
| Insert Hyperlink
|-
| Insert Header Default (toggle)
|-
| Insert Footer Default (toggle)
|-
| Insert Footnote...
|-
| Insert Caption...
|-
| Insert Bookmark...
|-
| Insert Cross-reference...
|-
| Insert Note...
|-
| Insert Script...
|-
| Insert Indexes and tables Entry...
|-
| Insert Indexes and tables Indexes and tables...
|-
| Insert Indexes and tables Bibliographic entry...
|-
| Insert Envelope...
|-
| Insert Frame... (param: number of columns)
|-
| Insert Table... (param: number of rows "x" number of columns; selection menu)
|-
| Insert Horizontal ruler...
|-
| Insert Picture From file... (param: file name)
|-
| Insert Picture Scan Select source...
|-
| Insert Picture Scan Request...
|-
| Insert Movie and sound... (param: file name)
|-
| Insert Object OLE object...
|-
| Insert Plug-in...
|-
| Insert Sound...
|-
| Insert Video...
|-
| Insert Applet...
|-
| Insert Formula
|-
| Insert Chart...
|-
| Insert Floating frame
|-
| Insert File...
|-
| Format Default formatting
|-
| Format Character...
|-
| Format Paragraph...
|-
| Format Bullets and numbering...
|-
| Format Page...
|-
| Format Change case Uppercase
|-
| Format Change case Lowercase
|-
| Format Columns...
|-
| Format Sections...
|-
| Format Styles and formatting
|-
| Format AutoFormat While typing (toggle)
|-
| Format AutoFormat Apply
|-
| Format AutoFormat Apply and edit changes
|-
| Format Anchor To page (alt1)
|-
| Format Anchor To Paragraph (alt2)
|-
| Format Anchor To Character (alt3)
|-
| Format Anchor As Character (alt4)
|-
| Format Anchor To Frame (alt5)
|-
| Format Wrap Wrap off (alt1)
|-
| Format Wrap Page wrap (alt2)
|-
| Format Wrap Optimal page wrap (alt3)
|-
| Format Wrap Wrap through (alt4)
|-
| Format Wrap In background (alt5)
|-
| Format Wrap Contour (alt6)
|-
| Format Wrap Edit contour...
|-
| Format Wrap First paragraph (alt7)
|-
| Format Wrap Edit...
|-
| Format Alignment Left (alt1)
|-
| Format Alignment Centered (alt2)
|-
| Format Alignment Right (alt3)
|-
| Format Alignment Justified (alt4)
|-
| Format Arrange Bring to front
|-
| Format Arrange Bring Forward
|-
| Format Arrange Send Backward
|-
| Format Arrange Send to Back
|-
| Format Arrange To foreground
|-
| Format Arrange To background
|-
| Format Flip Flip vertically
|-
| Format Flip Flip horizontally
|-
| Format Group Group
|-
| Format Group Ungroup
|-
| Format Group Enter group
|-
| Format Group Exit group
|-
| Format Object Position and size
|-
| Format Object Line...
|-
| Format Object Area...
|-
| Format Object Text attributes
|-
| Format Object Fontwork
|-
| Format Object Description...
|-
| Format Object Name...
|-
| Format Frame...
|-
| Format Picture...
|-
| Table Insert Table...
|-
| Table Insert Rows...
|-
| Table Insert Columns...
|-
| Table Delete Table
|-
| Table Delete Rows
|-
| Table Delete Columns
|-
| Table Select Table
|-
| Table Select Rows
|-
| Table Select Columns
|-
| Table Select Cells
|-
| Table Merge cells
|-
| Table Split cells
|-
| Table Protect cells
|-
| Table Merge table
|-
| Table Split table
|-
| Table AutoFormat...
|-
| Table Autofit Column width...
|-
| Table Autofit Optimal column width
|-
| Table Autofit Distribute columns evenly
|-
| Table Autofit Row height..
|-
| Table Autofit Optimal row height
|-
| Table Autofit Distribute rows equally
|-
| Table Autofit Allow row to break across pages and columns
|-
| Table Heading rows repeat
|-
| Table Convert Text to table...
|-
| Table Convert Table to text...
|-
| Table Sort...
|-
| Table Formula
|-
| Table Number format...
|-
| Table Table boundaries (toggle)
|-
| Table Table properties...
|-
| Tools Spellcheck...
|-
| Tools Language For selection English (USA) (alt1)
|-
| Tools Language For selection Swedish (Sweden) (alt2)
|-
| Tools Language For selection None (do not check spelling) (alt3)
|-
| Tools Language For selection More...
|-
| Tools Language For paragraph English (USA) (alt1)
|-
| Tools Language For paragraph Swedish (Sweden) (alt2)
|-
| Tools Language For paragraph None (do not check spelling) (alt3)
|-
| Tools Language For paragraph More...
|-
| Tools Language For all text English (USA) (alt1)
|-
| Tools Language For all text Swedish (Sweden) (alt2)
|-
| Tools Language For all text None (do not check spelling) (alt3)
|-
| Tools Language For all text More...
|-
| Tools Language Thesaurus...
|-
| Tools Language Hyphenation...
|-
| Tools Word count
|-
| Tools AutoCorrect...
|-
| Tools Online numbering...
|-
| Tools Line numbering...
|-
| Tools Footnotes...
|-
| Tools Gallery
|-
| Tools Media player
|-
| Tools Bibliography database
|-
| Tools Mail merge wizard...
|-
| Tools Sort...
|-
| Tools Calculate
|-
| Tools Update Update all
|-
| Tools Update Fields
|-
| Tools Update Links
|-
| Tools Update All charts
|-
| Tools Update Current index
|-
| Tools Update All indexes and tables
|-
| Tools Update Page formatting
|-
| Tools Macros Record macro
|-
| Tools Macros Run macro...
|-
| Tools Macros Organize macros OpenOffice.org Basic...
|-
| Tools Macros Organize macros Python...
|-
| Tools Macros Organize macros BeanShell...
|-
| Tools Macros Organize macros JavaScript...
|-
| Tools Macros Digital signature...
|-
| Tools Macros Organize dialogs...
|-
| Tools Extension manager...
|-
| Tools XML filter settings...
|-
| Tools Customize...
|-
| Tools Options...
|-
| Window New window
|-
| Window Close
|-
| Help OpenOffice.org help
|-
| Help What's this
|-
| Help Get help online...
|-
| Help Translate this applications...
|-
| Help Report a bug...
|-
| Help About OpenOffice.org
|}

== Tool bar buttons ==
Tool bars are sorted by approximate importance.

=== Text object propoerties ===
Font name...
Font size...
Bold
Italic (italicize)
Underline
Superscript (toggle) (show "Subscript on" or "Subscript off")
Subscript (toggle) (show "Superscript on" or "Superscript off")
Alignt left
Alignt right
Centered (align center)
Justified alignment

=== Formatting ===
Styles and formatting
Apply style
Line spacing: 1 (single spacing)
Line spacing: 1.5 (1.5 spacing)
Line spacing: 2 (double spacing)
Numbering on/off (toggle)
Bullets on/off (toggle)
Decrease indent
Increase indent
Font color...
Highlighting... (highlight, unhighlight)
Background colror...
Left-to-right
Right-to-left

=== Picture (image) ===
Insert image from file (get image from file; add image from file)
Filter...
Graphics mode...
Color
Transparency...
Flip horizontally
Flip vertically
Frame properties

=== Frame ===
Wrap off
Page wrap
Wrap through
Align left
Center horizontal
Align right
Align top
Align vertical center (center vertical)
Align bottom
Borders...
Line style...
Line color (color of the border)...
Background color ... (color menu; param: color)
Frame properties
Bring to front
Send to back
Change anchor...
Link frames
Unlink frames

=== Table ===
Insert table (see [[#Insert]]; param: number of rows, number of columns)
Line style...
Line color (of the border)...
Borders...
Background color...
Optimize...
Top
Center (vertical)
Bottom
AutoFormat (auto-format)
Table properties...
Sort
Sum

=== OLE-object ===
Apply style...
Align left
Align right
Align center horizontal
Align top
Align vertical
Align bottom
Wrap off
Page wrap
Wrap through
Frame properties
Bring to front
Send to back
Change anchor...
Borders...
Line style...
Border line color

=== Align ===
Left
Centered
Right
Top
Center [vertically]
Bottom

=== Fontwork ===
Fontwork gallery
Fontwork shape...
Fontwork same letter heights
Fontwork alignment...
Fontwork character spacing...

=== Formula ===
Formula text [text box]
Sum
Round
Percent
Square
Square root
Power
List separator
Equal
Not equal
Less than or equal
Greater than or equal
Less
Greater
Boolean Or
Boolean Xor
Boolean And
Boolean Not
Mean
Minimum
Maximum
Sine
Cosine
Tangent
Arcsine
Arccosine
Arctangent

=== Insert ===
Frame (param: number of columns)
AutoText [lots of options, not worth implementing]

=== Tools ===
Direct cursor on/off (toggle)
Hyphenation
Thesaurus
Graphics on/off (toggle)
Web layout/print layout (toggle)

=== Standard ===
Edit file (toggle)
AutoSpellcheck (auto-spellcheck, auto-spell-check)
Format paintbrush
Show draw functions (drawing tool bar)

=== Drawing ===
Select tool
Line
Freeform line
Text
Call-out
Points
Fontwork gallery
Image from file... (param: file name)
Extrusion on/off (toggle)

==== Shapes ====
Rectangle
Rectangle with rounded edges
Square
Square with rounded edges
Circle
Ellipse (oval)
Circle pie
Isosceles trianlge
Right triangle
Trapezoid (trapezium)
Diamond (rhombus)
Parallelogram
Regular pentagon
Regular hexagon
Regular octagon
Cross
Ring
Block-arc (rainbow, half-ring)
Cylinder
Cube
Folded corner
Frame

==== Symbol shapes ====
Smiley face (smiling face)
Sun
Moon
Lightning bolt
Heart
Flower
Cloud
"Prohibited" symbol
Puzzle
Double bracket
Left bracket
Right bracket
Double brace
Left brace
Right brace
Square bevel
Octagon bevel
Diamond bevel (rhombus bevel)

==== Block arrows ====
Left arrow
Right arrow
Up arrow
Down arrow
Left and right arrow (Double arrow horizontal)
Up and down arrow (Double arrow vertical)
Up and right arrow
Up, right and down arrow
4-way arrow (four-way arrow)
Corner right arrow
Split arrow
Striped right arrow
Notched right arrow
Pentagon
Chevron
Right arrow call-out
Left arrow call-out
Up arrow call-out
Down arrow call-out
Left and right arrow call-out
Up and down arrow call-out
Up and right arrow call-out
4-way arrow call-out (four-way arrow call-out)
Circular arrow
Right or left arrow
S-shaped arrow

==== Flowchart symbols ====
Process (square)
Alternative process (square with rounded corners)
Decision (rhombus, diamond)
Data (parallelogram)
Predefined process
Internal storage
Document
Multi-document
Terminator
Preparation (regular hexagon)
Manual input (vertical trapezium)
Manual operation (horizontal trapezium)
Connector (circle)
Off-page connector
Card
Punched tape
Summing junction
Or
Collate
Sort
Extract
Merge
Sorted data
Delay
Sequential access
Magnetic disc
Direct access storage
Display

==== Callouts (call-outs) ====
Rectangular call-out
Rounded rectangular call-out
Round call-out
Cloud call-out
Straight line call-out
Bent line call-out
Disconnected straight line call-out

==== Stars ====
Explosion
4-point star (four-point star)
5-point star (five-point star)
6-point star (six-point star, star of David)
8-point star (eight-point star)
12-point star (twelve-point star)
24-point star
6-point star, concave
Vertical scroll
Horizontal scroll
Signet
Doorplate

=== Form design ===
Select
Design mode on/off (toggle)
Control
Form
Form navigator
Add field
Activation order
Open in design mode
Automatic control focus
Position and size
Change anchor
Alignment (param: [[#Align]])
Display grid (show grid)
Snap to grid
Guides when moving (show guides when moving)

=== Form controls ===
Select
Design mode on/off (toggle)
Control
Form
Check box
Text box
Formatted fields
Push button
Option button
List box
Combo box
Label field
[[#Form design]]

==== More form controls ====
Spin button
Scroll bar
Image button
Image control
Date field
Time field
File selection
Numerical field
Currency field
Pattern field
Group box

=== Form navigation ===
Find record
Record
Absolute record
Text-record
Total no. of records (Total number of records)
First record
Previous record
Next record
Last record
New record
Save record
Undo: Data entry
Delete record
Refresh
Sort
Sort ascending
Sort descending
Auto filter
Apply filter
Form-based filters
Remove filter/sort
Data source as table

=== 3D settings ===
Extrusion on/off (toggle)
Tilt down
Tilt up
Tilt left
Tilt right
Depth...
Direction...
Lighting...
Surface...
3D color

=== Media playback ===
If any of the actions below are executed, the tool bar should appear.
Movie and sound
Play
Pause
Stop
Repeat
Mute
View ???

User Experience/Command search/Commands

2008-12-04T05:01:22Z

Pgan002: /* Main menu entries */

This page is for designing the names of commands and their synonyms. The items are shown as they appear in menu entries and button tool tips, followed by additional or replacement command names for each.

Items are listed only once: that is, if an item is listed as a menu entry, it should not be listed again as a button, and if it is listed as a button in one tool bar, it should not be listed in another tool bar. Button tool bars are shown in order of approximate importance.

== Main menu entries ==
{| class="table" border=1 
! Menu entry
! Command name
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Spreadsheet
| Create a new OpenOffice spreadsheet
|-
| File New Presentation
| Create a new presentation
|-
| File New Drawing
| Create a new drawing
|-
| File New HTML document
| create a new HTML document
|-
| File New XML form document
| Create a new XML document
|-
| File New Master document
| Create a new master document
|-
| File New Labels
|-
| File New Business cards
|-
| File New Templates and documents
|-
| File Open...
| Open document file
|-
| File Recent documents
|-
| File Wizards Letter...
|-
| File Wizards Fax...
|-
| File Wizards Agenda...
|-
| File Wizards Presentation...
|-
| File Wizards Web page...
|-
| File Wizards Document converter...
|-
| File Wizards Euro converter...
|-
| File Wizards Install new dictionaries...
|-
| File Close
| Close the current file
|-
| File Save
| Save the current file
|-
| File Save As...
| Save file as ...
|-
| File Reload
|-
| File Versions...
|-
| File Export...
|-
| File Export as PDF
|-
| File Send Document as e-mail
|-
| File Send E-mail as OpenDocument text...
|-
| File Send E-mail as Microsoft Word...
|-
| File Send E-mail as PDF...
|-
| File Send Create master document
|-
| File Send Create HTML document
|-
| File Send Outline to presentation
|-
| File Send Outline to Clipboard
|-
| File Send Create autoAbstract...
|-
| File Send AutoAbstract to presentation...
|-
| File Properties...
|-
| File Digital signatures...
|-
| File Templates Organize...
|-
| File Templates Save...
|-
| File Templates Edit...
|-
| File Preview in Web browser
|-
| File Page preview
|-
| File Print...
|-
| File Printer settings...
|-
| File exit
|-
| Edit (Can't) Undo (menu showing changes)
|-
| Edit (Can't) Redo (menu showing changes)
|-
| Edit (Can't) Repeat (action)
|-
| Edit Cut
|-
| Edit Copy
|-
| Edit Paste
|-
| Edit Paste special...
|-
| Edit Selection mode Standard
|-
| Edit Selection mode Block area
|-
| Edit Select all
|-
| Edit Changes Record (toggle)
|-
| Edit Changes Protect records...
|-
| Edit Changes Show (toggle)
|-
| Edit Changes Accept or reject...
|-
| Edit Changes Comment...
|-
| Edit Changes Merge document...
|-
| Edit Compare document...
|-
| Edit Find & replace...
|-
| Edit Navigator
|-
| Edit AutoText...
|-
| Edit Exchange database
|-
| Edit Fields...
|-
| Edit Footnote...
|-
| Edit Index entry...
|-
| Edit Bibliography entry...
|-
| Edit hyperlink
|-
| Edit Links...
|-
| Edit Plug-in
|-
| Edit Image map
|-
| Edit Object ???
|-
| View Print layout (alt1)
|-
| View Web layout (alt2)
|-
| View Toolbars 3D-settings (toggle)
|-
| View Toolbars Align (toggle)
|-
| View Toolbars Bullets and numbering (toggle)
|-
| View Toolbars Drawing (toggle)
|-
| View Toolbars Drawing object properties (toggle)
|-
| View Toolbars Font work (toggle)
|-
| View Toolbars Form controls (toggle)
|-
| View Toolbars Form design (toggle)
|-
| View Toolbars Form navigation (toggle)
|-
| View Toolbars Formatting (toggle)
|-
| View Toolbars Frame (toggle)
|-
| View Toolbars Insert (toggle)
|-
| View Toolbars Media playback (toggle)
|-
| View Toolbars OLE-Object (toggle)
|-
| View Toolbars Picture (toggle)
|-
| View Toolbars Standard (toggle)
|-
| View Toolbars Standard (viewing mode) (toggle)
|-
| View Toolbars Table (toggle)
|-
| View Toolbars Table object (toggle)
|-
| View Toolbars Text object (toggle)
|-
| View Toolbars Tools (toggle)
|-
| View Toolbars Hyperlink bar (toggle)
|-
| View Toolbars Formula (toggle)
|-
| View Toolbars Customize (toggle)
|-
| View Toolbars Reset (toggle)
|-
| View Status bar (toggle)
|-
| View Input methods status (toggle)
|-
| View Ruler (toggle)
|-
| View Text boundaries (toggle)
|-
| View Field shadings (toggle)
|-
| View Nonprinting Characters (toggle)
|-
| View Hidden paragraphs (toggle)
|-
| View Full screen
|-
| View Zoom...
|-
| Insert Manual break...
|-
| Insert Fields Date
|-
| Insert Fields Time
|-
| Insert Fields Page number
|-
| Insert Fields Page count
|-
| Insert Fields Subject
|-
| Insert Fields Title
|-
| Insert Fields Author
|-
| Insert Fields Other...
|-
| Insert Special character... (param: character name)
|-
| Insert Formatting mark Non-breaking space
|-
| Insert Formatting mark Non-breaking hyphen
|-
| Insert formatting mark Optional hyphen
|-
| Insert Section... (param: number of columns; menu to select visually)
|-
| Insert Hyperlink
|-
| Insert Header Default (toggle)
|-
| Insert Footer Default (toggle)
|-
| Insert Footnote...
|-
| Insert Caption...
|-
| Insert Bookmark...
|-
| Insert Cross-reference...
|-
| Insert Note...
|-
| Insert Script...
|-
| Insert Indexes and tables Entry...
|-
| Insert Indexes and tables Indexes and tables...
|-
| Insert Indexes and tables Bibliographic entry...
|-
| Insert Envelope...
|-
| Insert Frame... (param: number of columns)
|-
| Insert Table... (param: number of rows "x" number of columns; selection menu)
|-
| Insert Horizontal ruler...
|-
| Insert Picture From file... (param: file name)
|-
| Insert Picture Scan Select source...
|-
| Insert Picture Scan Request...
|-
| Insert Movie and sound... (param: file name)
|-
| Insert Object OLE object...
|-
| Insert Plug-in...
|-
| Insert Sound...
|-
| Insert Video...
|-
| Insert Applet...
|-
| Insert Formula
|-
| Insert Chart...
|-
| Insert Floating frame
|-
| Insert File...
|-
| Format Default formatting
|-
| Format Character...
|-
| Format Paragraph...
|-
| Format Bullets and numbering...
|-
| Format Page...
|-
| Format Change case Uppercase
|-
| Format Change case Lowercase
|-
| Format Columns...
|-
| Format Sections...
|-
| Format Styles and formatting
|-
| Format AutoFormat While typing (toggle)
|-
| Format AutoFormat Apply
|-
| Format AutoFormat Apply and edit changes
|-
| Format Anchor To page (alt1)
|-
| Format Anchor To Paragraph (alt2)
|-
| Format Anchor To Character (alt3)
|-
| Format Anchor As Character (alt4)
|-
| Format Anchor To Frame (alt5)
|-
| Format Wrap Wrap off (alt1)
|-
| Format Wrap Page wrap (alt2)
|-
| Format Wrap Optimal page wrap (alt3)
|-
| Format Wrap Wrap through (alt4)
|-
| Format Wrap In background (alt5)
|-
| Format Wrap Contour (alt6)
|-
| Format Wrap Edit contour...
|-
| Format Wrap First paragraph (alt7)
|-
| Format Wrap Edit...
|-
| Format Alignment Left (alt1)
|-
| Format Alignment Centered (alt2)
|-
| Format Alignment Right (alt3)
|-
| Format Alignment Justified (alt4)
|-
| Format Arrange Bring to front
|-
| Format Arrange Bring Forward
|-
| Format Arrange Send Backward
|-
| Format Arrange Send to Back
|-
| Format Arrange To foreground
|-
| Format Arrange To background
|-
| Format Flip Flip vertically
|-
| Format Flip Flip horizontally
|-
| Format Group Group
|-
| Format Group Ungroup
|-
| Format Group Enter group
|-
| Format Group Exit group
|-
| Format Object Position and size
|-
| Format Object Line...
|-
| Format Object Area...
|-
| Format Object Text attributes
|-
| Format Object Fontwork
|-
| Format Object Description...
|-
| Format Object Name...
|-
| Format Frame...
|-
| Format Picture...
|-
| Table Insert Table...
|-
| Table Insert Rows...
|-
| Table Insert Columns...
|-
| Table Delete Table
|-
| Table Delete Rows
|-
| Table Delete Columns
|-
| Table Select Table
|-
| Table Select Rows
|-
| Table Select Columns
|-
| Table Select Cells
|-
| Table Merge cells
|-
| Table Split cells
|-
| Table Protect cells
|-
| Table Merge table
|-
| Table Split table
|-
| Table AutoFormat...
|-
| Table Autofit Column width...
|-
| Table Autofit Optimal column width
|-
| Table Autofit Distribute columns evenly
|-
| Table Autofit Row height..
|-
| Table Autofit Optimal row height
|-
| Table Autofit Distribute rows equally
|-
| Table Autofit Allow row to break across pages and columns
|-
| Table Heading rows repeat
|-
| Table Convert Text to table...
|-
| Table Convert Table to text...
|-
| Table Sort...
|-
| Table Formula
|-
| Table Number format...
|-
| Table Table boundaries (toggle)
|-
| Table Table properties...
|-
| Tools Spellcheck...
|-
| Tools Language For selection English (USA) (alt1)
|-
| Tools Language For selection Swedish (Sweden) (alt2)
|-
| Tools Language For selection None (do not check spelling) (alt3)
|-
| Tools Language For selection More...
|-
| Tools Language For paragraph English (USA) (alt1)
|-
| Tools Language For paragraph Swedish (Sweden) (alt2)
|-
| Tools Language For paragraph None (do not check spelling) (alt3)
|-
| Tools Language For paragraph More...
|-
| Tools Language For all text English (USA) (alt1)
|-
| Tools Language For all text Swedish (Sweden) (alt2)
|-
| Tools Language For all text None (do not check spelling) (alt3)
|-
| Tools Language For all text More...
|-
| Tools Language Thesaurus...
|-
| Tools Language Hyphenation...
|-
| Tools Word count
|-
| Tools AutoCorrect...
|-
| Tools Online numbering...
|-
| Tools Line numbering...
|-
| Tools Footnotes...
|-
| Tools Gallery
|-
| Tools Media player
|-
| Tools Bibliography database
|-
| Tools Mail merge wizard...
|-
| Tools Sort...
|-
| Tools Calculate
|-
| Tools Update Update all
|-
| Tools Update Fields
|-
| Tools Update Links
|-
| Tools Update All charts
|-
| Tools Update Current index
|-
| Tools Update All indexes and tables
|-
| Tools Update Page formatting
|-
| Tools Macros Record macro
|-
| Tools Macros Run macro...
|-
| Tools Macros Organize macros OpenOffice.org Basic...
|-
| Tools Macros Organize macros Python...
|-
| Tools Macros Organize macros BeanShell...
|-
| Tools Macros Organize macros JavaScript...
|-
| Tools Macros Digital signature...
|-
| Tools Macros Organize dialogs...
|-
| Tools Extension manager...
|-
| Tools XML filter settings...
|-
| Tools Customize...
|-
| Tools Options...
|-
| Window New window
|-
| Window Close
|-
| Help OpenOffice.org help
|-
| Help What's this
|-
| Help Get help online...
|-
| Help Translate this applications...
|-
| Help Report a bug...
|-
| Help About OpenOffice.org
|}

== Tool bar buttons ==
Tool bars are sorted by approximate importance.

=== Text object propoerties ===
Font name...
Font size...
Bold
Italic (italicize)
Underline
Superscript (toggle) (show "Subscript on" or "Subscript off")
Subscript (toggle) (show "Superscript on" or "Superscript off")
Alignt left
Alignt right
Centered (align center)
Justified alignment

=== Formatting ===
Styles and formatting
Apply style
Line spacing: 1 (single spacing)
Line spacing: 1.5 (1.5 spacing)
Line spacing: 2 (double spacing)
Numbering on/off (toggle)
Bullets on/off (toggle)
Decrease indent
Increase indent
Font color...
Highlighting... (highlight, unhighlight)
Background colror...
Left-to-right
Right-to-left

=== Picture (image) ===
Insert image from file (get image from file; add image from file)
Filter...
Graphics mode...
Color
Transparency...
Flip horizontally
Flip vertically
Frame properties

=== Frame ===
Wrap off
Page wrap
Wrap through
Align left
Center horizontal
Align right
Align top
Align vertical center (center vertical)
Align bottom
Borders...
Line style...
Line color (color of the border)...
Background color ... (color menu; param: color)
Frame properties
Bring to front
Send to back
Change anchor...
Link frames
Unlink frames

=== Table ===
Insert table (see [[#Insert]]; param: number of rows, number of columns)
Line style...
Line color (of the border)...
Borders...
Background color...
Optimize...
Top
Center (vertical)
Bottom
AutoFormat (auto-format)
Table properties...
Sort
Sum

=== OLE-object ===
Apply style...
Align left
Align right
Align center horizontal
Align top
Align vertical
Align bottom
Wrap off
Page wrap
Wrap through
Frame properties
Bring to front
Send to back
Change anchor...
Borders...
Line style...
Border line color

=== Align ===
Left
Centered
Right
Top
Center [vertically]
Bottom

=== Fontwork ===
Fontwork gallery
Fontwork shape...
Fontwork same letter heights
Fontwork alignment...
Fontwork character spacing...

=== Formula ===
Formula text [text box]
Sum
Round
Percent
Square
Square root
Power
List separator
Equal
Not equal
Less than or equal
Greater than or equal
Less
Greater
Boolean Or
Boolean Xor
Boolean And
Boolean Not
Mean
Minimum
Maximum
Sine
Cosine
Tangent
Arcsine
Arccosine
Arctangent

=== Insert ===
Frame (param: number of columns)
AutoText [lots of options, not worth implementing]

=== Tools ===
Direct cursor on/off (toggle)
Hyphenation
Thesaurus
Graphics on/off (toggle)
Web layout/print layout (toggle)

=== Standard ===
Edit file (toggle)
AutoSpellcheck (auto-spellcheck, auto-spell-check)
Format paintbrush
Show draw functions (drawing tool bar)

=== Drawing ===
Select tool
Line
Freeform line
Text
Call-out
Points
Fontwork gallery
Image from file... (param: file name)
Extrusion on/off (toggle)

==== Shapes ====
Rectangle
Rectangle with rounded edges
Square
Square with rounded edges
Circle
Ellipse (oval)
Circle pie
Isosceles trianlge
Right triangle
Trapezoid (trapezium)
Diamond (rhombus)
Parallelogram
Regular pentagon
Regular hexagon
Regular octagon
Cross
Ring
Block-arc (rainbow, half-ring)
Cylinder
Cube
Folded corner
Frame

==== Symbol shapes ====
Smiley face (smiling face)
Sun
Moon
Lightning bolt
Heart
Flower
Cloud
"Prohibited" symbol
Puzzle
Double bracket
Left bracket
Right bracket
Double brace
Left brace
Right brace
Square bevel
Octagon bevel
Diamond bevel (rhombus bevel)

==== Block arrows ====
Left arrow
Right arrow
Up arrow
Down arrow
Left and right arrow (Double arrow horizontal)
Up and down arrow (Double arrow vertical)
Up and right arrow
Up, right and down arrow
4-way arrow (four-way arrow)
Corner right arrow
Split arrow
Striped right arrow
Notched right arrow
Pentagon
Chevron
Right arrow call-out
Left arrow call-out
Up arrow call-out
Down arrow call-out
Left and right arrow call-out
Up and down arrow call-out
Up and right arrow call-out
4-way arrow call-out (four-way arrow call-out)
Circular arrow
Right or left arrow
S-shaped arrow

==== Flowchart symbols ====
Process (square)
Alternative process (square with rounded corners)
Decision (rhombus, diamond)
Data (parallelogram)
Predefined process
Internal storage
Document
Multi-document
Terminator
Preparation (regular hexagon)
Manual input (vertical trapezium)
Manual operation (horizontal trapezium)
Connector (circle)
Off-page connector
Card
Punched tape
Summing junction
Or
Collate
Sort
Extract
Merge
Sorted data
Delay
Sequential access
Magnetic disc
Direct access storage
Display

==== Callouts (call-outs) ====
Rectangular call-out
Rounded rectangular call-out
Round call-out
Cloud call-out
Straight line call-out
Bent line call-out
Disconnected straight line call-out

==== Stars ====
Explosion
4-point star (four-point star)
5-point star (five-point star)
6-point star (six-point star, star of David)
8-point star (eight-point star)
12-point star (twelve-point star)
24-point star
6-point star, concave
Vertical scroll
Horizontal scroll
Signet
Doorplate

=== Form design ===
Select
Design mode on/off (toggle)
Control
Form
Form navigator
Add field
Activation order
Open in design mode
Automatic control focus
Position and size
Change anchor
Alignment (param: [[#Align]])
Display grid (show grid)
Snap to grid
Guides when moving (show guides when moving)

=== Form controls ===
Select
Design mode on/off (toggle)
Control
Form
Check box
Text box
Formatted fields
Push button
Option button
List box
Combo box
Label field
[[#Form design]]

==== More form controls ====
Spin button
Scroll bar
Image button
Image control
Date field
Time field
File selection
Numerical field
Currency field
Pattern field
Group box

=== Form navigation ===
Find record
Record
Absolute record
Text-record
Total no. of records (Total number of records)
First record
Previous record
Next record
Last record
New record
Save record
Undo: Data entry
Delete record
Refresh
Sort
Sort ascending
Sort descending
Auto filter
Apply filter
Form-based filters
Remove filter/sort
Data source as table

=== 3D settings ===
Extrusion on/off (toggle)
Tilt down
Tilt up
Tilt left
Tilt right
Depth...
Direction...
Lighting...
Surface...
3D color

=== Media playback ===
If any of the actions below are executed, the tool bar should appear.
Movie and sound
Play
Pause
Stop
Repeat
Mute
View ???

User Experience/Command search/Commands

2008-12-04T05:00:19Z

Pgan002: /* Tool bar buttons */

This page is for designing the names of commands and their synonyms. The items are shown as they appear in menu entries and button tool tips, followed by additional or replacement command names for each.

Items are listed only once: that is, if an item is listed as a menu entry, it should not be listed again as a button, and if it is listed as a button in one tool bar, it should not be listed in another tool bar. Button tool bars are shown in order of approximate importance.

== Main menu entries ==
{| class="table" border=1 
! Menu entry
! Command name
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Spreadsheet
| Create a new OpenOffice spreadsheet
|-
| File New Presentation
| Create a new presentation
|-
| File New Drawing
| create a new drawing
|-
| File New HTML document
| create a new HTML document
|-
| File New XML form document
| create a new XML document
|-
| File New Master document
| create a new master document
|-
| File New Labels
|-
| File New Business cards
|-
| File New Templates and documents
|-
| File Open...
| open document file
|-
| File Recent documents
|-
| File Wizards Letter...
|-
| File Wizards Fax...
|-
| File Wizards Agenda...
|-
| File Wizards Presentation...
|-
| File Wizards Web page...
|-
| File Wizards Document converter...
|-
| File Wizards Euro converter...
|-
| File Wizards Install new dictionaries...
|-
| File Close
| close the current file
|-
| File Save
| save the current file
|-
| File Save As...
| save file as ...
|-
| File Reload
|-
| File Versions...
|-
| File Export...
|-
| File Export as PDF
|-
| File Send Document as e-mail
|-
| File Send E-mail as OpenDocument text...
|-
| File Send E-mail as Microsoft Word...
|-
| File Send E-mail as PDF...
|-
| File Send Create master document
|-
| File Send Create HTML document
|-
| File Send Outline to presentation
|-
| File Send Outline to Clipboard
|-
| File Send Create autoAbstract...
|-
| File Send AutoAbstract to presentation...
|-
| File Properties...
|-
| File Digital signatures...
|-
| File Templates Organize...
|-
| File Templates Save...
|-
| File Templates Edit...
|-
| File Preview in Web browser
|-
| File Page preview
|-
| File Print...
|-
| File Printer settings...
|-
| File exit
|-
| Edit (Can't) Undo (menu showing changes)
|-
| Edit (Can't) Redo (menu showing changes)
|-
| Edit (Can't) Repeat (action)
|-
| Edit Cut
|-
| Edit Copy
|-
| Edit Paste
|-
| Edit Paste special...
|-
| Edit Selection mode Standard
|-
| Edit Selection mode Block area
|-
| Edit Select all
|-
| Edit Changes Record (toggle)
|-
| Edit Changes Protect records...
|-
| Edit Changes Show (toggle)
|-
| Edit Changes Accept or reject...
|-
| Edit Changes Comment...
|-
| Edit Changes Merge document...
|-
| Edit Compare document...
|-
| Edit Find & replace...
|-
| Edit Navigator
|-
| Edit AutoText...
|-
| Edit Exchange database
|-
| Edit Fields...
|-
| Edit Footnote...
|-
| Edit Index entry...
|-
| Edit Bibliography entry...
|-
| Edit hyperlink
|-
| Edit Links...
|-
| Edit Plug-in
|-
| Edit Image map
|-
| Edit Object ???
|-
| View Print layout (alt1)
|-
| View Web layout (alt2)
|-
| View Toolbars 3D-settings (toggle)
|-
| View Toolbars Align (toggle)
|-
| View Toolbars Bullets and numbering (toggle)
|-
| View Toolbars Drawing (toggle)
|-
| View Toolbars Drawing object properties (toggle)
|-
| View Toolbars Font work (toggle)
|-
| View Toolbars Form controls (toggle)
|-
| View Toolbars Form design (toggle)
|-
| View Toolbars Form navigation (toggle)
|-
| View Toolbars Formatting (toggle)
|-
| View Toolbars Frame (toggle)
|-
| View Toolbars Insert (toggle)
|-
| View Toolbars Media playback (toggle)
|-
| View Toolbars OLE-Object (toggle)
|-
| View Toolbars Picture (toggle)
|-
| View Toolbars Standard (toggle)
|-
| View Toolbars Standard (viewing mode) (toggle)
|-
| View Toolbars Table (toggle)
|-
| View Toolbars Table object (toggle)
|-
| View Toolbars Text object (toggle)
|-
| View Toolbars Tools (toggle)
|-
| View Toolbars Hyperlink bar (toggle)
|-
| View Toolbars Formula (toggle)
|-
| View Toolbars Customize (toggle)
|-
| View Toolbars Reset (toggle)
|-
| View Status bar (toggle)
|-
| View Input methods status (toggle)
|-
| View Ruler (toggle)
|-
| View Text boundaries (toggle)
|-
| View Field shadings (toggle)
|-
| View Nonprinting Characters (toggle)
|-
| View Hidden paragraphs (toggle)
|-
| View Full screen
|-
| View Zoom...
|-
| Insert Manual break...
|-
| Insert Fields Date
|-
| Insert Fields Time
|-
| Insert Fields Page number
|-
| Insert Fields Page count
|-
| Insert Fields Subject
|-
| Insert Fields Title
|-
| Insert Fields Author
|-
| Insert Fields Other...
|-
| Insert Special character... (param: character name)
|-
| Insert Formatting mark Non-breaking space
|-
| Insert Formatting mark Non-breaking hyphen
|-
| Insert formatting mark Optional hyphen
|-
| Insert Section... (param: number of columns; menu to select visually)
|-
| Insert Hyperlink
|-
| Insert Header Default (toggle)
|-
| Insert Footer Default (toggle)
|-
| Insert Footnote...
|-
| Insert Caption...
|-
| Insert Bookmark...
|-
| Insert Cross-reference...
|-
| Insert Note...
|-
| Insert Script...
|-
| Insert Indexes and tables Entry...
|-
| Insert Indexes and tables Indexes and tables...
|-
| Insert Indexes and tables Bibliographic entry...
|-
| Insert Envelope...
|-
| Insert Frame... (param: number of columns)
|-
| Insert Table... (param: number of rows "x" number of columns; selection menu)
|-
| Insert Horizontal ruler...
|-
| Insert Picture From file... (param: file name)
|-
| Insert Picture Scan Select source...
|-
| Insert Picture Scan Request...
|-
| Insert Movie and sound... (param: file name)
|-
| Insert Object OLE object...
|-
| Insert Plug-in...
|-
| Insert Sound...
|-
| Insert Video...
|-
| Insert Applet...
|-
| Insert Formula
|-
| Insert Chart...
|-
| Insert Floating frame
|-
| Insert File...
|-
| Format Default formatting
|-
| Format Character...
|-
| Format Paragraph...
|-
| Format Bullets and numbering...
|-
| Format Page...
|-
| Format Change case Uppercase
|-
| Format Change case Lowercase
|-
| Format Columns...
|-
| Format Sections...
|-
| Format Styles and formatting
|-
| Format AutoFormat While typing (toggle)
|-
| Format AutoFormat Apply
|-
| Format AutoFormat Apply and edit changes
|-
| Format Anchor To page (alt1)
|-
| Format Anchor To Paragraph (alt2)
|-
| Format Anchor To Character (alt3)
|-
| Format Anchor As Character (alt4)
|-
| Format Anchor To Frame (alt5)
|-
| Format Wrap Wrap off (alt1)
|-
| Format Wrap Page wrap (alt2)
|-
| Format Wrap Optimal page wrap (alt3)
|-
| Format Wrap Wrap through (alt4)
|-
| Format Wrap In background (alt5)
|-
| Format Wrap Contour (alt6)
|-
| Format Wrap Edit contour...
|-
| Format Wrap First paragraph (alt7)
|-
| Format Wrap Edit...
|-
| Format Alignment Left (alt1)
|-
| Format Alignment Centered (alt2)
|-
| Format Alignment Right (alt3)
|-
| Format Alignment Justified (alt4)
|-
| Format Arrange Bring to front
|-
| Format Arrange Bring Forward
|-
| Format Arrange Send Backward
|-
| Format Arrange Send to Back
|-
| Format Arrange To foreground
|-
| Format Arrange To background
|-
| Format Flip Flip vertically
|-
| Format Flip Flip horizontally
|-
| Format Group Group
|-
| Format Group Ungroup
|-
| Format Group Enter group
|-
| Format Group Exit group
|-
| Format Object Position and size
|-
| Format Object Line...
|-
| Format Object Area...
|-
| Format Object Text attributes
|-
| Format Object Fontwork
|-
| Format Object Description...
|-
| Format Object Name...
|-
| Format Frame...
|-
| Format Picture...
|-
| Table Insert Table...
|-
| Table Insert Rows...
|-
| Table Insert Columns...
|-
| Table Delete Table
|-
| Table Delete Rows
|-
| Table Delete Columns
|-
| Table Select Table
|-
| Table Select Rows
|-
| Table Select Columns
|-
| Table Select Cells
|-
| Table Merge cells
|-
| Table Split cells
|-
| Table Protect cells
|-
| Table Merge table
|-
| Table Split table
|-
| Table AutoFormat...
|-
| Table Autofit Column width...
|-
| Table Autofit Optimal column width
|-
| Table Autofit Distribute columns evenly
|-
| Table Autofit Row height..
|-
| Table Autofit Optimal row height
|-
| Table Autofit Distribute rows equally
|-
| Table Autofit Allow row to break across pages and columns
|-
| Table Heading rows repeat
|-
| Table Convert Text to table...
|-
| Table Convert Table to text...
|-
| Table Sort...
|-
| Table Formula
|-
| Table Number format...
|-
| Table Table boundaries (toggle)
|-
| Table Table properties...
|-
| Tools Spellcheck...
|-
| Tools Language For selection English (USA) (alt1)
|-
| Tools Language For selection Swedish (Sweden) (alt2)
|-
| Tools Language For selection None (do not check spelling) (alt3)
|-
| Tools Language For selection More...
|-
| Tools Language For paragraph English (USA) (alt1)
|-
| Tools Language For paragraph Swedish (Sweden) (alt2)
|-
| Tools Language For paragraph None (do not check spelling) (alt3)
|-
| Tools Language For paragraph More...
|-
| Tools Language For all text English (USA) (alt1)
|-
| Tools Language For all text Swedish (Sweden) (alt2)
|-
| Tools Language For all text None (do not check spelling) (alt3)
|-
| Tools Language For all text More...
|-
| Tools Language Thesaurus...
|-
| Tools Language Hyphenation...
|-
| Tools Word count
|-
| Tools AutoCorrect...
|-
| Tools Online numbering...
|-
| Tools Line numbering...
|-
| Tools Footnotes...
|-
| Tools Gallery
|-
| Tools Media player
|-
| Tools Bibliography database
|-
| Tools Mail merge wizard...
|-
| Tools Sort...
|-
| Tools Calculate
|-
| Tools Update Update all
|-
| Tools Update Fields
|-
| Tools Update Links
|-
| Tools Update All charts
|-
| Tools Update Current index
|-
| Tools Update All indexes and tables
|-
| Tools Update Page formatting
|-
| Tools Macros Record macro
|-
| Tools Macros Run macro...
|-
| Tools Macros Organize macros OpenOffice.org Basic...
|-
| Tools Macros Organize macros Python...
|-
| Tools Macros Organize macros BeanShell...
|-
| Tools Macros Organize macros JavaScript...
|-
| Tools Macros Digital signature...
|-
| Tools Macros Organize dialogs...
|-
| Tools Extension manager...
|-
| Tools XML filter settings...
|-
| Tools Customize...
|-
| Tools Options...
|-
| Window New window
|-
| Window Close
|-
| Help OpenOffice.org help
|-
| Help What's this
|-
| Help Get help online...
|-
| Help Translate this applications...
|-
| Help Report a bug...
|-
| Help About OpenOffice.org
|}

== Tool bar buttons ==
Tool bars are sorted by approximate importance.

=== Text object propoerties ===
Font name...
Font size...
Bold
Italic (italicize)
Underline
Superscript (toggle) (show "Subscript on" or "Subscript off")
Subscript (toggle) (show "Superscript on" or "Superscript off")
Alignt left
Alignt right
Centered (align center)
Justified alignment

=== Formatting ===
Styles and formatting
Apply style
Line spacing: 1 (single spacing)
Line spacing: 1.5 (1.5 spacing)
Line spacing: 2 (double spacing)
Numbering on/off (toggle)
Bullets on/off (toggle)
Decrease indent
Increase indent
Font color...
Highlighting... (highlight, unhighlight)
Background colror...
Left-to-right
Right-to-left

=== Picture (image) ===
Insert image from file (get image from file; add image from file)
Filter...
Graphics mode...
Color
Transparency...
Flip horizontally
Flip vertically
Frame properties

=== Frame ===
Wrap off
Page wrap
Wrap through
Align left
Center horizontal
Align right
Align top
Align vertical center (center vertical)
Align bottom
Borders...
Line style...
Line color (color of the border)...
Background color ... (color menu; param: color)
Frame properties
Bring to front
Send to back
Change anchor...
Link frames
Unlink frames

=== Table ===
Insert table (see [[#Insert]]; param: number of rows, number of columns)
Line style...
Line color (of the border)...
Borders...
Background color...
Optimize...
Top
Center (vertical)
Bottom
AutoFormat (auto-format)
Table properties...
Sort
Sum

=== OLE-object ===
Apply style...
Align left
Align right
Align center horizontal
Align top
Align vertical
Align bottom
Wrap off
Page wrap
Wrap through
Frame properties
Bring to front
Send to back
Change anchor...
Borders...
Line style...
Border line color

=== Align ===
Left
Centered
Right
Top
Center [vertically]
Bottom

=== Fontwork ===
Fontwork gallery
Fontwork shape...
Fontwork same letter heights
Fontwork alignment...
Fontwork character spacing...

=== Formula ===
Formula text [text box]
Sum
Round
Percent
Square
Square root
Power
List separator
Equal
Not equal
Less than or equal
Greater than or equal
Less
Greater
Boolean Or
Boolean Xor
Boolean And
Boolean Not
Mean
Minimum
Maximum
Sine
Cosine
Tangent
Arcsine
Arccosine
Arctangent

=== Insert ===
Frame (param: number of columns)
AutoText [lots of options, not worth implementing]

=== Tools ===
Direct cursor on/off (toggle)
Hyphenation
Thesaurus
Graphics on/off (toggle)
Web layout/print layout (toggle)

=== Standard ===
Edit file (toggle)
AutoSpellcheck (auto-spellcheck, auto-spell-check)
Format paintbrush
Show draw functions (drawing tool bar)

=== Drawing ===
Select tool
Line
Freeform line
Text
Call-out
Points
Fontwork gallery
Image from file... (param: file name)
Extrusion on/off (toggle)

==== Shapes ====
Rectangle
Rectangle with rounded edges
Square
Square with rounded edges
Circle
Ellipse (oval)
Circle pie
Isosceles trianlge
Right triangle
Trapezoid (trapezium)
Diamond (rhombus)
Parallelogram
Regular pentagon
Regular hexagon
Regular octagon
Cross
Ring
Block-arc (rainbow, half-ring)
Cylinder
Cube
Folded corner
Frame

==== Symbol shapes ====
Smiley face (smiling face)
Sun
Moon
Lightning bolt
Heart
Flower
Cloud
"Prohibited" symbol
Puzzle
Double bracket
Left bracket
Right bracket
Double brace
Left brace
Right brace
Square bevel
Octagon bevel
Diamond bevel (rhombus bevel)

==== Block arrows ====
Left arrow
Right arrow
Up arrow
Down arrow
Left and right arrow (Double arrow horizontal)
Up and down arrow (Double arrow vertical)
Up and right arrow
Up, right and down arrow
4-way arrow (four-way arrow)
Corner right arrow
Split arrow
Striped right arrow
Notched right arrow
Pentagon
Chevron
Right arrow call-out
Left arrow call-out
Up arrow call-out
Down arrow call-out
Left and right arrow call-out
Up and down arrow call-out
Up and right arrow call-out
4-way arrow call-out (four-way arrow call-out)
Circular arrow
Right or left arrow
S-shaped arrow

==== Flowchart symbols ====
Process (square)
Alternative process (square with rounded corners)
Decision (rhombus, diamond)
Data (parallelogram)
Predefined process
Internal storage
Document
Multi-document
Terminator
Preparation (regular hexagon)
Manual input (vertical trapezium)
Manual operation (horizontal trapezium)
Connector (circle)
Off-page connector
Card
Punched tape
Summing junction
Or
Collate
Sort
Extract
Merge
Sorted data
Delay
Sequential access
Magnetic disc
Direct access storage
Display

==== Callouts (call-outs) ====
Rectangular call-out
Rounded rectangular call-out
Round call-out
Cloud call-out
Straight line call-out
Bent line call-out
Disconnected straight line call-out

==== Stars ====
Explosion
4-point star (four-point star)
5-point star (five-point star)
6-point star (six-point star, star of David)
8-point star (eight-point star)
12-point star (twelve-point star)
24-point star
6-point star, concave
Vertical scroll
Horizontal scroll
Signet
Doorplate

=== Form design ===
Select
Design mode on/off (toggle)
Control
Form
Form navigator
Add field
Activation order
Open in design mode
Automatic control focus
Position and size
Change anchor
Alignment (param: [[#Align]])
Display grid (show grid)
Snap to grid
Guides when moving (show guides when moving)

=== Form controls ===
Select
Design mode on/off (toggle)
Control
Form
Check box
Text box
Formatted fields
Push button
Option button
List box
Combo box
Label field
[[#Form design]]

==== More form controls ====
Spin button
Scroll bar
Image button
Image control
Date field
Time field
File selection
Numerical field
Currency field
Pattern field
Group box

=== Form navigation ===
Find record
Record
Absolute record
Text-record
Total no. of records (Total number of records)
First record
Previous record
Next record
Last record
New record
Save record
Undo: Data entry
Delete record
Refresh
Sort
Sort ascending
Sort descending
Auto filter
Apply filter
Form-based filters
Remove filter/sort
Data source as table

=== 3D settings ===
Extrusion on/off (toggle)
Tilt down
Tilt up
Tilt left
Tilt right
Depth...
Direction...
Lighting...
Surface...
3D color

=== Media playback ===
If any of the actions below are executed, the tool bar should appear.
Movie and sound
Play
Pause
Stop
Repeat
Mute
View ???

User Experience/Command search/Commands

2008-12-04T04:42:14Z

Pgan002: /* Main menu entries */

This page is for designing the names of commands and their synonyms. The items are shown as they appear in menu entries and button tool tips, followed by additional or replacement command names for each.

Items are listed only once: that is, if an item is listed as a menu entry, it should not be listed again as a button, and if it is listed as a button in one tool bar, it should not be listed in another tool bar. Button tool bars are shown in order of approximate importance.

== Main menu entries ==
{| class="table" border=1 
! Menu entry
! Command name
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Text document
| Create a new OpenOffice text document
|-
| File New Spreadsheet
| Create a new OpenOffice spreadsheet
|-
| File New Presentation
| Create a new presentation
|-
| File New Drawing
| create a new drawing
|-
| File New HTML document
| create a new HTML document
|-
| File New XML form document
| create a new XML document
|-
| File New Master document
| create a new master document
|-
| File New Labels
|-
| File New Business cards
|-
| File New Templates and documents
|-
| File Open...
| open document file
|-
| File Recent documents
|-
| File Wizards Letter...
|-
| File Wizards Fax...
|-
| File Wizards Agenda...
|-
| File Wizards Presentation...
|-
| File Wizards Web page...
|-
| File Wizards Document converter...
|-
| File Wizards Euro converter...
|-
| File Wizards Install new dictionaries...
|-
| File Close
| close the current file
|-
| File Save
| save the current file
|-
| File Save As...
| save file as ...
|-
| File Reload
|-
| File Versions...
|-
| File Export...
|-
| File Export as PDF
|-
| File Send Document as e-mail
|-
| File Send E-mail as OpenDocument text...
|-
| File Send E-mail as Microsoft Word...
|-
| File Send E-mail as PDF...
|-
| File Send Create master document
|-
| File Send Create HTML document
|-
| File Send Outline to presentation
|-
| File Send Outline to Clipboard
|-
| File Send Create autoAbstract...
|-
| File Send AutoAbstract to presentation...
|-
| File Properties...
|-
| File Digital signatures...
|-
| File Templates Organize...
|-
| File Templates Save...
|-
| File Templates Edit...
|-
| File Preview in Web browser
|-
| File Page preview
|-
| File Print...
|-
| File Printer settings...
|-
| File exit
|-
| Edit (Can't) Undo (menu showing changes)
|-
| Edit (Can't) Redo (menu showing changes)
|-
| Edit (Can't) Repeat (action)
|-
| Edit Cut
|-
| Edit Copy
|-
| Edit Paste
|-
| Edit Paste special...
|-
| Edit Selection mode Standard
|-
| Edit Selection mode Block area
|-
| Edit Select all
|-
| Edit Changes Record (toggle)
|-
| Edit Changes Protect records...
|-
| Edit Changes Show (toggle)
|-
| Edit Changes Accept or reject...
|-
| Edit Changes Comment...
|-
| Edit Changes Merge document...
|-
| Edit Compare document...
|-
| Edit Find & replace...
|-
| Edit Navigator
|-
| Edit AutoText...
|-
| Edit Exchange database
|-
| Edit Fields...
|-
| Edit Footnote...
|-
| Edit Index entry...
|-
| Edit Bibliography entry...
|-
| Edit hyperlink
|-
| Edit Links...
|-
| Edit Plug-in
|-
| Edit Image map
|-
| Edit Object ???
|-
| View Print layout (alt1)
|-
| View Web layout (alt2)
|-
| View Toolbars 3D-settings (toggle)
|-
| View Toolbars Align (toggle)
|-
| View Toolbars Bullets and numbering (toggle)
|-
| View Toolbars Drawing (toggle)
|-
| View Toolbars Drawing object properties (toggle)
|-
| View Toolbars Font work (toggle)
|-
| View Toolbars Form controls (toggle)
|-
| View Toolbars Form design (toggle)
|-
| View Toolbars Form navigation (toggle)
|-
| View Toolbars Formatting (toggle)
|-
| View Toolbars Frame (toggle)
|-
| View Toolbars Insert (toggle)
|-
| View Toolbars Media playback (toggle)
|-
| View Toolbars OLE-Object (toggle)
|-
| View Toolbars Picture (toggle)
|-
| View Toolbars Standard (toggle)
|-
| View Toolbars Standard (viewing mode) (toggle)
|-
| View Toolbars Table (toggle)
|-
| View Toolbars Table object (toggle)
|-
| View Toolbars Text object (toggle)
|-
| View Toolbars Tools (toggle)
|-
| View Toolbars Hyperlink bar (toggle)
|-
| View Toolbars Formula (toggle)
|-
| View Toolbars Customize (toggle)
|-
| View Toolbars Reset (toggle)
|-
| View Status bar (toggle)
|-
| View Input methods status (toggle)
|-
| View Ruler (toggle)
|-
| View Text boundaries (toggle)
|-
| View Field shadings (toggle)
|-
| View Nonprinting Characters (toggle)
|-
| View Hidden paragraphs (toggle)
|-
| View Full screen
|-
| View Zoom...
|-
| Insert Manual break...
|-
| Insert Fields Date
|-
| Insert Fields Time
|-
| Insert Fields Page number
|-
| Insert Fields Page count
|-
| Insert Fields Subject
|-
| Insert Fields Title
|-
| Insert Fields Author
|-
| Insert Fields Other...
|-
| Insert Special character... (param: character name)
|-
| Insert Formatting mark Non-breaking space
|-
| Insert Formatting mark Non-breaking hyphen
|-
| Insert formatting mark Optional hyphen
|-
| Insert Section... (param: number of columns; menu to select visually)
|-
| Insert Hyperlink
|-
| Insert Header Default (toggle)
|-
| Insert Footer Default (toggle)
|-
| Insert Footnote...
|-
| Insert Caption...
|-
| Insert Bookmark...
|-
| Insert Cross-reference...
|-
| Insert Note...
|-
| Insert Script...
|-
| Insert Indexes and tables Entry...
|-
| Insert Indexes and tables Indexes and tables...
|-
| Insert Indexes and tables Bibliographic entry...
|-
| Insert Envelope...
|-
| Insert Frame... (param: number of columns)
|-
| Insert Table... (param: number of rows "x" number of columns; selection menu)
|-
| Insert Horizontal ruler...
|-
| Insert Picture From file... (param: file name)
|-
| Insert Picture Scan Select source...
|-
| Insert Picture Scan Request...
|-
| Insert Movie and sound... (param: file name)
|-
| Insert Object OLE object...
|-
| Insert Plug-in...
|-
| Insert Sound...
|-
| Insert Video...
|-
| Insert Applet...
|-
| Insert Formula
|-
| Insert Chart...
|-
| Insert Floating frame
|-
| Insert File...
|-
| Format Default formatting
|-
| Format Character...
|-
| Format Paragraph...
|-
| Format Bullets and numbering...
|-
| Format Page...
|-
| Format Change case Uppercase
|-
| Format Change case Lowercase
|-
| Format Columns...
|-
| Format Sections...
|-
| Format Styles and formatting
|-
| Format AutoFormat While typing (toggle)
|-
| Format AutoFormat Apply
|-
| Format AutoFormat Apply and edit changes
|-
| Format Anchor To page (alt1)
|-
| Format Anchor To Paragraph (alt2)
|-
| Format Anchor To Character (alt3)
|-
| Format Anchor As Character (alt4)
|-
| Format Anchor To Frame (alt5)
|-
| Format Wrap Wrap off (alt1)
|-
| Format Wrap Page wrap (alt2)
|-
| Format Wrap Optimal page wrap (alt3)
|-
| Format Wrap Wrap through (alt4)
|-
| Format Wrap In background (alt5)
|-
| Format Wrap Contour (alt6)
|-
| Format Wrap Edit contour...
|-
| Format Wrap First paragraph (alt7)
|-
| Format Wrap Edit...
|-
| Format Alignment Left (alt1)
|-
| Format Alignment Centered (alt2)
|-
| Format Alignment Right (alt3)
|-
| Format Alignment Justified (alt4)
|-
| Format Arrange Bring to front
|-
| Format Arrange Bring Forward
|-
| Format Arrange Send Backward
|-
| Format Arrange Send to Back
|-
| Format Arrange To foreground
|-
| Format Arrange To background
|-
| Format Flip Flip vertically
|-
| Format Flip Flip horizontally
|-
| Format Group Group
|-
| Format Group Ungroup
|-
| Format Group Enter group
|-
| Format Group Exit group
|-
| Format Object Position and size
|-
| Format Object Line...
|-
| Format Object Area...
|-
| Format Object Text attributes
|-
| Format Object Fontwork
|-
| Format Object Description...
|-
| Format Object Name...
|-
| Format Frame...
|-
| Format Picture...
|-
| Table Insert Table...
|-
| Table Insert Rows...
|-
| Table Insert Columns...
|-
| Table Delete Table
|-
| Table Delete Rows
|-
| Table Delete Columns
|-
| Table Select Table
|-
| Table Select Rows
|-
| Table Select Columns
|-
| Table Select Cells
|-
| Table Merge cells
|-
| Table Split cells
|-
| Table Protect cells
|-
| Table Merge table
|-
| Table Split table
|-
| Table AutoFormat...
|-
| Table Autofit Column width...
|-
| Table Autofit Optimal column width
|-
| Table Autofit Distribute columns evenly
|-
| Table Autofit Row height..
|-
| Table Autofit Optimal row height
|-
| Table Autofit Distribute rows equally
|-
| Table Autofit Allow row to break across pages and columns
|-
| Table Heading rows repeat
|-
| Table Convert Text to table...
|-
| Table Convert Table to text...
|-
| Table Sort...
|-
| Table Formula
|-
| Table Number format...
|-
| Table Table boundaries (toggle)
|-
| Table Table properties...
|-
| Tools Spellcheck...
|-
| Tools Language For selection English (USA) (alt1)
|-
| Tools Language For selection Swedish (Sweden) (alt2)
|-
| Tools Language For selection None (do not check spelling) (alt3)
|-
| Tools Language For selection More...
|-
| Tools Language For paragraph English (USA) (alt1)
|-
| Tools Language For paragraph Swedish (Sweden) (alt2)
|-
| Tools Language For paragraph None (do not check spelling) (alt3)
|-
| Tools Language For paragraph More...
|-
| Tools Language For all text English (USA) (alt1)
|-
| Tools Language For all text Swedish (Sweden) (alt2)
|-
| Tools Language For all text None (do not check spelling) (alt3)
|-
| Tools Language For all text More...
|-
| Tools Language Thesaurus...
|-
| Tools Language Hyphenation...
|-
| Tools Word count
|-
| Tools AutoCorrect...
|-
| Tools Online numbering...
|-
| Tools Line numbering...
|-
| Tools Footnotes...
|-
| Tools Gallery
|-
| Tools Media player
|-
| Tools Bibliography database
|-
| Tools Mail merge wizard...
|-
| Tools Sort...
|-
| Tools Calculate
|-
| Tools Update Update all
|-
| Tools Update Fields
|-
| Tools Update Links
|-
| Tools Update All charts
|-
| Tools Update Current index
|-
| Tools Update All indexes and tables
|-
| Tools Update Page formatting
|-
| Tools Macros Record macro
|-
| Tools Macros Run macro...
|-
| Tools Macros Organize macros OpenOffice.org Basic...
|-
| Tools Macros Organize macros Python...
|-
| Tools Macros Organize macros BeanShell...
|-
| Tools Macros Organize macros JavaScript...
|-
| Tools Macros Digital signature...
|-
| Tools Macros Organize dialogs...
|-
| Tools Extension manager...
|-
| Tools XML filter settings...
|-
| Tools Customize...
|-
| Tools Options...
|-
| Window New window
|-
| Window Close
|-
| Help OpenOffice.org help
|-
| Help What's this
|-
| Help Get help online...
|-
| Help Translate this applications...
|-
| Help Report a bug...
|-
| Help About OpenOffice.org
|}

== Tool bar buttons ==
Sorted by approximate order importance.

=== Text object propoerties ===
Font name...
Font size...
Bold
Italic (italicize)
Underline
Superscript (toggle) (show "Subscript on" or "Subscript off")
Subscript (toggle) (show "Superscript on" or "Superscript off")
Alignt left
Alignt right
Centered (align center)
Justified alignment

=== Formatting ===
Styles and formatting
Apply style
Line spacing: 1 (single spacing)
Line spacing: 1.5 (1.5 spacing)
Line spacing: 2 (double spacing)
Numbering on/off (toggle)
Bullets on/off (toggle)
Decrease indent
Increase indent
Font color...
Highlighting... (highlight, unhighlight)
Background colror...
Left-to-right
Right-to-left

=== Picture (image) ===
Insert image from file (get image from file; add image from file)
Filter...
Graphics mode...
Color
Transparency...
Flip horizontally
Flip vertically
Frame properties

=== Frame ===
Wrap off
Page wrap
Wrap through
Align left
Center horizontal
Align right
Align top
Align vertical center (center vertical)
Align bottom
Borders...
Line style...
Line color (color of the border)...
Background color ... (color menu; param: color)
Frame properties
Bring to front
Send to back
Change anchor...
Link frames
Unlink frames

=== Table ===
Insert table (see [[#Insert]]; param: number of rows, number of columns)
Line style...
Line color (of the border)...
Borders...
Background color...
Optimize...
Top
Center (vertical)
Bottom
AutoFormat (auto-format)
Table properties...
Sort
Sum

=== OLE-object ===
Apply style...
Align left
Align right
Align center horizontal
Align top
Align vertical
Align bottom
Wrap off
Page wrap
Wrap through
Frame properties
Bring to front
Send to back
Change anchor...
Borders...
Line style...
Border line color

=== Align ===
Left
Centered
Right
Top
Center [vertically]
Bottom

=== Fontwork ===
Fontwork gallery
Fontwork shape...
Fontwork same letter heights
Fontwork alignment...
Fontwork character spacing...

=== Formula ===
Formula text [text box]
Sum
Round
Percent
Square
Square root
Power
List separator
Equal
Not equal
Less than or equal
Greater than or equal
Less
Greater
Boolean Or
Boolean Xor
Boolean And
Boolean Not
Mean
Minimum
Maximum
Sine
Cosine
Tangent
Arcsine
Arccosine
Arctangent

=== Insert ===
Frame (param: number of columns)
AutoText [lots of options, not worth implementing]

=== Tools ===
Direct cursor on/off (toggle)
Hyphenation
Thesaurus
Graphics on/off (toggle)
Web layout/print layout (toggle)

=== Standard ===
Edit file (toggle)
AutoSpellcheck (auto-spellcheck, auto-spell-check)
Format paintbrush
Show draw functions (drawing tool bar)

=== Drawing ===
Select tool
Line
Freeform line
Text
Call-out
Points
Fontwork gallery
Image from file... (param: file name)
Extrusion on/off (toggle)

==== Shapes ====
Rectangle
Rectangle with rounded edges
Square
Square with rounded edges
Circle
Ellipse (oval)
Circle pie
Isosceles trianlge
Right triangle
Trapezoid (trapezium)
Diamond (rhombus)
Parallelogram
Regular pentagon
Regular hexagon
Regular octagon
Cross
Ring
Block-arc (rainbow, half-ring)
Cylinder
Cube
Folded corner
Frame

==== Symbol shapes ====
Smiley face (smiling face)
Sun
Moon
Lightning bolt
Heart
Flower
Cloud
"Prohibited" symbol
Puzzle
Double bracket
Left bracket
Right bracket
Double brace
Left brace
Right brace
Square bevel
Octagon bevel
Diamond bevel (rhombus bevel)

==== Block arrows ====
Left arrow
Right arrow
Up arrow
Down arrow
Left and right arrow (Double arrow horizontal)
Up and down arrow (Double arrow vertical)
Up and right arrow
Up, right and down arrow
4-way arrow (four-way arrow)
Corner right arrow
Split arrow
Striped right arrow
Notched right arrow
Pentagon
Chevron
Right arrow call-out
Left arrow call-out
Up arrow call-out
Down arrow call-out
Left and right arrow call-out
Up and down arrow call-out
Up and right arrow call-out
4-way arrow call-out (four-way arrow call-out)
Circular arrow
Right or left arrow
S-shaped arrow

==== Flowchart symbols ====
Process (square)
Alternative process (square with rounded corners)
Decision (rhombus, diamond)
Data (parallelogram)
Predefined process
Internal storage
Document
Multi-document
Terminator
Preparation (regular hexagon)
Manual input (vertical trapezium)
Manual operation (horizontal trapezium)
Connector (circle)
Off-page connector
Card
Punched tape
Summing junction
Or
Collate
Sort
Extract
Merge
Sorted data
Delay
Sequential access
Magnetic disc
Direct access storage
Display

==== Callouts (call-outs) ====
Rectangular call-out
Rounded rectangular call-out
Round call-out
Cloud call-out
Straight line call-out
Bent line call-out
Disconnected straight line call-out

==== Stars ====
Explosion
4-point star (four-point star)
5-point star (five-point star)
6-point star (six-point star, star of David)
8-point star (eight-point star)
12-point star (twelve-point star)
24-point star
6-point star, concave
Vertical scroll
Horizontal scroll
Signet
Doorplate

=== Form design ===
Select
Design mode on/off (toggle)
Control
Form
Form navigator
Add field
Activation order
Open in design mode
Automatic control focus
Position and size
Change anchor
Alignment (param: [[#Align]])
Display grid (show grid)
Snap to grid
Guides when moving (show guides when moving)

=== Form controls ===
Select
Design mode on/off (toggle)
Control
Form
Check box
Text box
Formatted fields
Push button
Option button
List box
Combo box
Label field
[[#Form design]]

==== More form controls ====
Spin button
Scroll bar
Image button
Image control
Date field
Time field
File selection
Numerical field
Currency field
Pattern field
Group box

=== Form navigation ===
Find record
Record
Absolute record
Text-record
Total no. of records (Total number of records)
First record
Previous record
Next record
Last record
New record
Save record
Undo: Data entry
Delete record
Refresh
Sort
Sort ascending
Sort descending
Auto filter
Apply filter
Form-based filters
Remove filter/sort
Data source as table

=== 3D settings ===
Extrusion on/off (toggle)
Tilt down
Tilt up
Tilt left
Tilt right
Depth...
Direction...
Lighting...
Surface...
3D color

=== Media playback ===
If any of the actions below are executed, the tool bar should appear.
Movie and sound
Play
Pause
Stop
Repeat
Mute
View ???

User Experience/Command search

2008-12-04T04:26:53Z

Pgan002: /* Related projects */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words.

The command box should appear next to the menu bar, right-aligned. It should contain the label "Type what you want to do (F7)" in faint color. The label disappears when the box is focused. A tool tip appears on mouse over, saying "Type in the box to invoke a command, e.g. 'insert table'".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, e.g. 'insert table'". Jim starts typing "insert table" and sees a list of commands, appear. Thus he understands what the box is for. When he needs to add a formula inside Writer, he focuses the command box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Command box placement ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Apart from their canonical name (e.g. "insert picture") commands may have synonym names ("add picture"). Synonyms can be created by hand, using the text in the Help, and a thesaurus. The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by alphabetical order, by frecency, or by date of addition.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
It may be useful to reveal the menu item for the selected command's (if there is a menu item), as in MacOS. But that would be too slow, distracting and would not encourage the user to use the command. Instead, we can highlight the enclosing menu in the menu bar (and the rest of the path path to the item) without; the user can open the menus if she is interested. Alternatively, each result that corresponds to a menu item can have an icon at the right edge, that when clicked opens the menu to reveal the item.

This command facility will not be included in the MacOSX version of OOo, at least initially, until it is better than the system search for menu items under the Help menu.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* MacOS X applications have a command box in the Help menu.
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far, but the code may be useful for implementing this current proposal.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font and right-aligned box
* Create a mock-up of the unfocused command box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command name for each menu item and button
* Add synonymous names where required
* Convert this document into a specification
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search

2008-12-04T04:25:40Z

Pgan002: /* Other details */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words.

The command box should appear next to the menu bar, right-aligned. It should contain the label "Type what you want to do (F7)" in faint color. The label disappears when the box is focused. A tool tip appears on mouse over, saying "Type in the box to invoke a command, e.g. 'insert table'".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, e.g. 'insert table'". Jim starts typing "insert table" and sees a list of commands, appear. Thus he understands what the box is for. When he needs to add a formula inside Writer, he focuses the command box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Command box placement ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Apart from their canonical name (e.g. "insert picture") commands may have synonym names ("add picture"). Synonyms can be created by hand, using the text in the Help, and a thesaurus. The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by alphabetical order, by frecency, or by date of addition.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
It may be useful to reveal the menu item for the selected command's (if there is a menu item), as in MacOS. But that would be too slow, distracting and would not encourage the user to use the command. Instead, we can highlight the enclosing menu in the menu bar (and the rest of the path path to the item) without; the user can open the menus if she is interested. Alternatively, each result that corresponds to a menu item can have an icon at the right edge, that when clicked opens the menu to reveal the item.

This command facility will not be included in the MacOSX version of OOo, at least initially, until it is better than the system search for menu items under the Help menu.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* MacOS X's command box in the Help menu of many MacOS applications.
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font and right-aligned box
* Create a mock-up of the unfocused command box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command name for each menu item and button
* Add synonymous names where required
* Convert this document into a specification
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search

2008-12-04T04:25:18Z

Pgan002: /* Other details */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words.

The command box should appear next to the menu bar, right-aligned. It should contain the label "Type what you want to do (F7)" in faint color. The label disappears when the box is focused. A tool tip appears on mouse over, saying "Type in the box to invoke a command, e.g. 'insert table'".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, e.g. 'insert table'". Jim starts typing "insert table" and sees a list of commands, appear. Thus he understands what the box is for. When he needs to add a formula inside Writer, he focuses the command box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Command box placement ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Apart from their canonical name (e.g. "insert picture") commands may have synonym names ("add picture"). Synonyms can be created by hand, using the text in the Help, and a thesaurus. The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by alphabetical order, by frecency, or by date of addition.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
It may be useful to reveal the menu item for the selected command's (if there is a menu item), as in MacOS. But that would be too slow, distracting and would not encourage the user to use the command. Instead, we can highlight the enclosing menu in the menu bar (and the rest of the path path to the item) without; the user can open the menus if she is interested. Alternatively, each result that corresponds to a menu item can have an icon at the right edge, that when clicked opens the menu to reveal the item.

This facility would not be included in the MacOSX version of OOo, at least initially, until it is better than the system search for menu items under the Help menu.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* MacOS X's command box in the Help menu of many MacOS applications.
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font and right-aligned box
* Create a mock-up of the unfocused command box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command name for each menu item and button
* Add synonymous names where required
* Convert this document into a specification
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search

2008-12-04T04:22:21Z

Pgan002:

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words.

The command box should appear next to the menu bar, right-aligned. It should contain the label "Type what you want to do (F7)" in faint color. The label disappears when the box is focused. A tool tip appears on mouse over, saying "Type in the box to invoke a command, e.g. 'insert table'".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, e.g. 'insert table'". Jim starts typing "insert table" and sees a list of commands, appear. Thus he understands what the box is for. When he needs to add a formula inside Writer, he focuses the command box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Command box placement ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Apart from their canonical name (e.g. "insert picture") commands may have synonym names ("add picture"). Synonyms can be created by hand, using the text in the Help, and a thesaurus. The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by alphabetical order, by frecency, or by date of addition.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
It may be useful to reveal the menu item for the selected command's (if there is a menu item), as in MacOS. But that would be too slow, distracting and would not encourage the user to use the command. Instead, we can highlight the enclosing menu in the menu bar (and the rest of the path path to the item) without; the user can open the menus if she is interested. Alternatively, each result that corresponds to a menu item can have an icon at the right edge, that when clicked opens the menu to reveal the item.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* MacOS X's command box in the Help menu of many MacOS applications.
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font and right-aligned box
* Create a mock-up of the unfocused command box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command name for each menu item and button
* Add synonymous names where required
* Convert this document into a specification
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search

2008-11-28T06:01:06Z

Pgan002: /* Other details */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. Commands have a canonical name (e.g. "insert picture") and may have synonym names ("add picture").

The command box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type in the box to invoke a command (e.g. 'insert table')".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, such as "insert table". Jim understands what the box is for, thanks to this message and his familiarity with Web search and desktop search. When he needs to add a formula inside Writer, he focuses the command box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Command box placement ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
It may be useful to reveal the menu item for the selected command's (if there is a menu item), as in MacOS. But that would be too slow, distracting and would not encourage the user to use the command. Instead, we can highlight the enclosing menu in the menu bar (and the rest of the path path to the item) without; the user can open the menus if she is interested. Alternatively, each result that corresponds to a menu item can have an icon at the right edge, that when clicked opens the menu to reveal the item.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* MacOS X's command box in the Help menu of many MacOS applications.
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the command box tool tip
* Create a mock-up of the unfocused command box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command name for each menu item and button
* Add synonymous names where required
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search

2008-11-28T05:52:42Z

Pgan002: /* To do */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. Commands have a canonical name (e.g. "insert picture") and may have synonym names ("add picture").

The command box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type in the box to invoke a command (e.g. 'insert table')".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, such as "insert table". Jim understands what the box is for, thanks to this message and his familiarity with Web search and desktop search. When he needs to add a formula inside Writer, he focuses the command box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Command box placement ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* MacOS X's command box in the Help menu of many MacOS applications.
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the command box tool tip
* Create a mock-up of the unfocused command box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command name for each menu item and button
* Add synonymous names where required
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search

2008-11-28T05:52:24Z

Pgan002: /* To do */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. Commands have a canonical name (e.g. "insert picture") and may have synonym names ("add picture").

The command box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type in the box to invoke a command (e.g. 'insert table')".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, such as "insert table". Jim understands what the box is for, thanks to this message and his familiarity with Web search and desktop search. When he needs to add a formula inside Writer, he focuses the command box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Command box placement ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* MacOS X's command box in the Help menu of many MacOS applications.
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the command box tool tip
* Create a mock-up of the unfocused command box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command name for each menu item and button
* Add synonymous names where required
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]
<math><math>Insert formula here</math></math>

User Experience/Command search

2008-11-28T05:52:04Z

Pgan002: /* Related projects */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. Commands have a canonical name (e.g. "insert picture") and may have synonym names ("add picture").

The command box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type in the box to invoke a command (e.g. 'insert table')".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, such as "insert table". Jim understands what the box is for, thanks to this message and his familiarity with Web search and desktop search. When he needs to add a formula inside Writer, he focuses the command box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Command box placement ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* MacOS X's command box in the Help menu of many MacOS applications.
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the command box tool tip
* Create a mock-up of the unfocused command box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command for each menu item and button
* Add synonymous names where required
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]
<math><math>Insert formula here</math></math>

User Experience/Command search

2008-11-28T05:47:44Z

Pgan002: search box -> command box

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. Commands have a canonical name (e.g. "insert picture") and may have synonym names ("add picture").

The command box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type in the box to invoke a command (e.g. 'insert table')".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, such as "insert table". Jim understands what the box is for, thanks to this message and his familiarity with Web search and desktop search. When he needs to add a formula inside Writer, he focuses the command box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Command box placement ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the command box tool tip
* Create a mock-up of the unfocused command box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command for each menu item and button
* Add synonymous names where required
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]
<math><math>Insert formula here</math></math>

User Experience/Command search

2008-11-28T05:46:13Z

Pgan002: /* Use case */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. Commands have a canonical name (e.g. "insert picture") and may have synonym names ("add picture").

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type in the box to invoke a command (e.g. 'insert table')".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "type what you want to do" to the right of the top menus. Curious, he points the mouse pointer at it, and sees the tool tip "Type in the box to invoke a command, such as "insert table". Jim understands what the box is for, thanks to this message and his familiarity with Web search and desktop search. When he needs to add a formula inside Writer, he focuses the search box and types "formula". Three items appear below the box, saying "View Formula tool bar", "Insert formula" and "Table formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement of the search box ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command for each menu item and button
* Add synonymous names where required
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]
<math><math>Insert formula here</math></math>

User Experience/Command search

2008-11-28T05:41:35Z

Pgan002: /* Use case */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. Commands have a canonical name (e.g. "insert picture") and may have synonym names ("add picture").

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type in the box to invoke a command (e.g. 'insert table')".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.2, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement of the search box ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command for each menu item and button
* Add synonymous names where required
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]
<math><math>Insert formula here</math></math>

User Experience/Command search

2008-11-28T02:04:29Z

Pgan002: /* To do */

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. Commands have a canonical name (e.g. "insert picture") and may have synonym names ("add picture").

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type in the box to invoke a command (e.g. 'insert table')".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.0, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement of the search box ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of menu items and buttons</strike>
* Create a command for each menu item and button
* Add synonymous names where required
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]
<math><math>Insert formula here</math></math>

User Experience/Command search/Commands

2008-11-28T02:01:45Z

Pgan002: /* Media playback */

This page is for designing the names of commands and their synonyms. The items are shown as they appear in menu entries and button tool tips, followed by additional or replacement command names for each.

Items are listed only once: that is, if an item is listed as a menu entry, it should not be listed again as a button, and if it is listed as a button in one tool bar, it should not be listed in another tool bar. Button tool bars are shown in order of approximate importance.

== Main menu entries ==
File New Text document
* Create a new OpenOffice text document
File New Spreadsheet
* Create a new OpenOffice spreadsheet
File New Presentation
* Create a new presentation
File New Drawing
* create a new drawing
File New HTML document
* create a new HTML document
File New XML form document
* create a new XML document
File New Master document
* create a new master document
File New Labels
File New Business cards
File New Templates and documents
File Open...
* open document file
File Recent documents
File Wizards Letter...
File Wizards Fax...
File Wizards Agenda...
File Wizards Presentation...
File Wizards Web page...
File Wizards Document converter...
File Wizards Euro converter...
File Wizards Install new dictionaries...
File Close
* close the current file
File Save
* save the current file
File Save As...
* save file as ...
File Reload
File Versions...
File Export...
File Export as PDF
File Send Document as e-mail
File Send E-mail as OpenDocument text...
File Send E-mail as Microsoft Word...
File Send E-mail as PDF...
File Send Create master document
File Send Create HTML document
File Send Outline to presentation
File Send Outline to Clipboard
File Send Create autoAbstract...
File Send AutoAbstract to presentation...
File Properties...
File Digital signatures...
File Templates Organize...
File Templates Save...
File Templates Edit...
File Preview in Web browser
File Page preview
File Print...
File Printer settings...
File exit
Edit (Can't) Undo (menu showing changes)
Edit (Can't) Redo (menu showing changes)
Edit (Can't) Repeat (action)
Edit Cut
Edit Copy
Edit Paste
Edit Paste special...
Edit Selecion mode Standard
Edit Selection mode Block area
Edit Select all
Edit Changes Record (toggle)
Edit Changes Protect records...
Edit Changes Show (toggle)
Edit Changes Accept or reject...
Edit Changes Commone...
Edit Changes Merge document...
Edit Compare document...
Edit Find & replace...
Edit Navigator
Edit AutoText...
Edit Exchange database
Edit Fields...
Edit Footnote...
Edit Index entry...
Edit Bibliography entry...
Edit hyperlink
Edit Links...
Edit Plug-in
Edit Image map
Edit Object ???
View Print layout (alt1)
View Web layout (alt2)
View Toolbars 3D-settings (toggle)
View Toolbars Align (toggle)
View Toolbars Bullets and numbering (toggle)
View Toolbars Drawing (toggle)
View Toolbars Drawing object properties (toggle)
View Toolbars Font work (toggle)
View Toolbars Form controls (toggle)
View Toolbars Form design (toggle)
View Toolbars Form navigation (toggle)
View Toolbars Formatting (toggle)
View Toolbars Frame (toggle)
View Toolbars Insert (toggle)
View Toolbars Media playback (toggle)
View Toolbars OLE-Object (toggle)
View Toolbars Picture (toggle)
View Toolbars Standard (toggle)
View Toolbars Standard (viewing mode) (toggle)
View Toolbars Table (toggle)
View Toolbars Table object (toggle)
View Toolbars Text object (toggle)
View Toolbars Tools (toggle)
View Toolbars Hyperlink bar (toggle)
View Toolbars Formula (toggle)
View Toolbars Customize (toggle)
View Toolbars Reset (toggle)
View Status bar (toggle)
View Input methods status (toggle)
View Ruler (toggle)
View Text boundaries (toggle)
View Field shadings (toggle)
View Nonprinting Characters (toggle)
View Hidden paragraphs (toggle)
View Full screen
View Zoom...
Insert Manual break...
Insert Fields Date
Insert Fields Time
Insert Fields Page number
Insert Fields Page count
Insert Fields Subject
Insert Fields Title
Insert Fields Author
insert Fields Other...
Insert Special character... (param: character name)
Insert Formatting mark Non-breaking space
Insert Formatting mark Non-breaking hyphen
Insert formatting mark Optional hyphen
Insert Section... (param: number of columns; menu to select visually)
Insert Hyperlink
Insert Header Default (toggle)
Insert Footer Default (toggle)
Insert Footnote...
Insert Caption...
Insert Bookmark...
Insert Cross-reference...
Insert Note...
Insert Script...
Insert Indexes and tables Entry...
Insert Indexes and tables Indexes and tables...
Insert Indexes and tables Bibliographic entry...
Insert Envelope...
Insert Frame... (param: number of columns)
Insert Table... (param: number of rows "x" number of columns; selection menu)
Insert Horizontal ruler...
Insert Picture From file... (param: file name)
Insert Picture Scan Select source...
Insert Picture Scan Request...
Insert Movie and sound... (param: file name)
Insert Object OLE object...
Insert Plug-in...
Insert Sound...
Insert Video...
Insert Applet...
Insert Formula
Insert Chart...
Insert Floating frame
Insert File...
Format Default formatting
Format Character...
Format Paragraph...
Format Bullets and numbering...
Format Page...
Format Change case Uppercase
Format Change case Lowercase
Format Columns...
Format Sections...
Format Styles and formatting
Format AutoFormat While typing (toggle)
Format AutoFormat Apply
Format AutoFormat Apply and edit changes
Format Anchor To page (alt1)
Format Anchor To Paragraph (alt2)
Format Anchor To Character (alt3)
Format Anchor As Character (alt4)
Format Anchor To Frame (alt5)
Format Wrap Wrap off (alt1)
Format Wrap Page wrap (alt2)
Format Wrap Optimal page wrap (alt3)
Format Wrap Wrap through (alt4)
Format Wrap In background (alt5)
Format Wrap Contour (alt6)
Format Wrap Edit contour...
Format Wrap First paragraph (alt7)
Format Wrap Edit...
Format Alignment Left (alt1)
Format Alignment Centered (alt2)
Format Alignment Right (alt3)
Format Alignment Justified (alt4)
Format Arrange Bring to front
Format Arrange Bring Forward
Format Arrange Send Backward
Format Arrange Send to Back
Format Arrange To foreground
Format Arrange To background
Format Flip Flip vertically
Format Flip Flip horizontally
Format Group Group
Format Group Ungroup
Format Group Enter group
Format Group Exit group
Format Object Position and size
Format Object Line...
Format Object Area...
Format Object Text attributes
Format Object Fontwork
Format Object Description...
Format Object Name...
Format Frame...
Format Picture...
Table Insert Table...
Table Insert Rows...
Table Insert Columns...
Table Delete Table
Table Delete Rows
Table Delete Columns
Table Select Table
Table Select Rows
Table Select Columns
Table Select Cells
Table Merge cells
Table Split cells
Table Protect cells
Table Merge table
Table Split table
Table AutoFormat...
Table Autofit Column width...
Table Autofit Optimal column width
Table Autofit Distribute columns evenly
Table Autofit Row height..
Table Autofit Optimal row height
Table Autofit Distribute rows equally
Table Autofit Allow row to break across pages and columns
Table Heading rows repeat
Table Convert Text to table...
Table Convert Table to text...
Table Sort...
Table Formula
Table Number format...
Table Table boundaries (toggle)
Table Table properties...
Tools Spellcheck...
Tools Language For selection English (USA) (alt1)
Tools Language For selection Swedish (Sweden) (alt2)
Tools Language For selection None (do not check spelling) (alt3)
Tools Language For selection More...
Tools Language For paragraph English (USA) (alt1)
Tools Language For paragraph Swedish (Sweden) (alt2)
Tools Language For paragraph None (do not check spelling) (alt3)
Tools Language For paragraph More...
Tools Language For all text English (USA) (alt1)
Tools Language For all text Swedish (Sweden) (alt2)
Tools Language For all text None (do not check spelling) (alt3)
Tools Language For all text More...
Tools Language Thesaurus...
Tools Language Hyphenation...
Tools Word count
Tools AutoCorrect...
Tools Online numbering...
Tools Line numbering...
Tools Footnotes...
Tools Gallery
Tools Media player
Tools Bibliography database
Tools Mail merge wizard...
Tools Sort...
Tools Calculate
Tools Update Update all
Tools Update Fields
Tools Update Links
Tools Update All charts
Tools Update Current index
Tools Update All indexes and tables
Tools Update Page formatting
Tools Macros Record macro
Tools Macros Run macro...
Tools Macros Organize macros OpenOffice.org Basic...
Tools Macros Organize macros Python...
Tools Macros Organize macros BeanShell...
Tools Macros Organize macros JavaScript...
Tools Macros Digital signature...
Tools Macros Organize dialogs...
Tools Extension manager...
Tools XML filter settings...
Tools Customize...
Tools Options...
Window New window
Window Close
Help OpenOffice.org help
Help What's this
Help Get help online...
Help Translate this applications...
Help Report a bug...
Help About OpenOffice.org

== Tool bar buttons ==
Sorted by approximate order importance.

=== Text object propoerties ===
Font name...
Font size...
Bold
Italic (italicize)
Underline
Superscript (toggle) (show "Subscript on" or "Subscript off")
Subscript (toggle) (show "Superscript on" or "Superscript off")
Alignt left
Alignt right
Centered (align center)
Justified alignment

=== Formatting ===
Styles and formatting
Apply style
Line spacing: 1 (single spacing)
Line spacing: 1.5 (1.5 spacing)
Line spacing: 2 (double spacing)
Numbering on/off (toggle)
Bullets on/off (toggle)
Decrease indent
Increase indent
Font color...
Highlighting... (highlight, unhighlight)
Background colror...
Left-to-right
Right-to-left

=== Picture (image) ===
Insert image from file (get image from file; add image from file)
Filter...
Graphics mode...
Color
Transparency...
Flip horizontally
Flip vertically
Frame properties

=== Frame ===
Wrap off
Page wrap
Wrap through
Align left
Center horizontal
Align right
Align top
Align vertical center (center vertical)
Align bottom
Borders...
Line style...
Line color (color of the border)...
Background color ... (color menu; param: color)
Frame properties
Bring to front
Send to back
Change anchor...
Link frames
Unlink frames

=== Table ===
Insert table (see [[#Insert]]; param: number of rows, number of columns)
Line style...
Line color (of the border)...
Borders...
Background color...
Optimize...
Top
Center (vertical)
Bottom
AutoFormat (auto-format)
Table properties...
Sort
Sum

=== OLE-object ===
Apply style...
Align left
Align right
Align center horizontal
Align top
Align vertical
Align bottom
Wrap off
Page wrap
Wrap through
Frame properties
Bring to front
Send to back
Change anchor...
Borders...
Line style...
Border line color

=== Align ===
Left
Centered
Right
Top
Center [vertically]
Bottom

=== Fontwork ===
Fontwork gallery
Fontwork shape...
Fontwork same letter heights
Fontwork alignment...
Fontwork character spacing...

=== Formula ===
Formula text [text box]
Sum
Round
Percent
Square
Square root
Power
List separator
Equal
Not equal
Less than or equal
Greater than or equal
Less
Greater
Boolean Or
Boolean Xor
Boolean And
Boolean Not
Mean
Minimum
Maximum
Sine
Cosine
Tangent
Arcsine
Arccosine
Arctangent

=== Insert ===
Frame (param: number of columns)
AutoText [lots of options, not worth implementing]

=== Tools ===
Direct cursor on/off (toggle)
Hyphenation
Thesaurus
Graphics on/off (toggle)
Web layout/print layout (toggle)

=== Standard ===
Edit file (toggle)
AutoSpellcheck (auto-spellcheck, auto-spell-check)
Format paintbrush
Show draw functions (drawing tool bar)

=== Drawing ===
Select tool
Line
Freeform line
Text
Call-out
Points
Fontwork gallery
Image from file... (param: file name)
Extrusion on/off (toggle)

==== Shapes ====
Rectangle
Rectangle with rounded edges
Square
Square with rounded edges
Circle
Ellipse (oval)
Circle pie
Isosceles trianlge
Right triangle
Trapezoid (trapezium)
Diamond (rhombus)
Parallelogram
Regular pentagon
Regular hexagon
Regular octagon
Cross
Ring
Block-arc (rainbow, half-ring)
Cylinder
Cube
Folded corner
Frame

==== Symbol shapes ====
Smiley face (smiling face)
Sun
Moon
Lightning bolt
Heart
Flower
Cloud
"Prohibited" symbol
Puzzle
Double bracket
Left bracket
Right bracket
Double brace
Left brace
Right brace
Square bevel
Octagon bevel
Diamond bevel (rhombus bevel)

==== Block arrows ====
Left arrow
Right arrow
Up arrow
Down arrow
Left and right arrow (Double arrow horizontal)
Up and down arrow (Double arrow vertical)
Up and right arrow
Up, right and down arrow
4-way arrow (four-way arrow)
Corner right arrow
Split arrow
Striped right arrow
Notched right arrow
Pentagon
Chevron
Right arrow call-out
Left arrow call-out
Up arrow call-out
Down arrow call-out
Left and right arrow call-out
Up and down arrow call-out
Up and right arrow call-out
4-way arrow call-out (four-way arrow call-out)
Circular arrow
Right or left arrow
S-shaped arrow

==== Flowchart symbols ====
Process (square)
Alternative process (square with rounded corners)
Decision (rhombus, diamond)
Data (parallelogram)
Predefined process
Internal storage
Document
Multi-document
Terminator
Preparation (regular hexagon)
Manual input (vertical trapezium)
Manual operation (horizontal trapezium)
Connector (circle)
Off-page connector
Card
Punched tape
Summing junction
Or
Collate
Sort
Extract
Merge
Sorted data
Delay
Sequential access
Magnetic disc
Direct access storage
Display

==== Callouts (call-outs) ====
Rectangular call-out
Rounded rectangular call-out
Round call-out
Cloud call-out
Straight line call-out
Bent line call-out
Disconnected straight line call-out

==== Stars ====
Explosion
4-point star (four-point star)
5-point star (five-point star)
6-point star (six-point star, star of David)
8-point star (eight-point star)
12-point star (twelve-point star)
24-point star
6-point star, concave
Vertical scroll
Horizontal scroll
Signet
Doorplate

=== Form design ===
Select
Design mode on/off (toggle)
Control
Form
Form navigator
Add field
Activation order
Open in design mode
Automatic control focus
Position and size
Change anchor
Alignment (param: [[#Align]])
Display grid (show grid)
Snap to grid
Guides when moving (show guides when moving)

=== Form controls ===
Select
Design mode on/off (toggle)
Control
Form
Check box
Text box
Formatted fields
Push button
Option button
List box
Combo box
Label field
[[#Form design]]

==== More form controls ====
Spin button
Scroll bar
Image button
Image control
Date field
Time field
File selection
Numerical field
Currency field
Pattern field
Group box

=== Form navigation ===
Find record
Record
Absolute record
Text-record
Total no. of records (Total number of records)
First record
Previous record
Next record
Last record
New record
Save record
Undo: Data entry
Delete record
Refresh
Sort
Sort ascending
Sort descending
Auto filter
Apply filter
Form-based filters
Remove filter/sort
Data source as table

=== 3D settings ===
Extrusion on/off (toggle)
Tilt down
Tilt up
Tilt left
Tilt right
Depth...
Direction...
Lighting...
Surface...
3D color

=== Media playback ===
If any of the actions below are executed, the tool bar should appear.
Movie and sound
Play
Pause
Stop
Repeat
Mute
View ???

User Experience/Command search

2008-11-28T01:58:25Z

Pgan002:

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse. They feel frustrated and powerless to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. Commands have a canonical name (e.g. "insert picture") and may have synonym names ("add picture").

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type in the box to invoke a command (e.g. 'insert table')".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.0, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement of the search box ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of command names of menu items</strike>
* Add synonymous names
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]
<math><math>Insert formula here</math></math>

User Experience/Command search

2008-11-28T01:54:46Z

Pgan002:

This document is a design of a way to interact with OpenOffice applications using commands. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus and tool bars, users spend a lot of time and effort searching through the menus, usually using the mouse, and feel frustrated and powerless for not being able to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. Commands have a canonical name (e.g. "insert picture") and may have synonym names ("add picture").

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type in the box to invoke a command (e.g. 'insert table')".

[[Image:OO_command_bar_proposal.png|600px|Command box mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.0, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement of the search box ==

Several places for putting the command (search) box were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command box next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command box, just like a URL bar in a web browser. If the window gets too small, the box may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search box, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of command names of menu items</strike>
* Add synonymous names
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]
<math><math>Insert formula here</math></math>

User Experience/Command search

2008-11-28T01:46:10Z

Pgan002: /* Other details */

This is a design of a new, simple way to interact with OpenOffice applications. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus, users spend a lot of time and concentration manually searching the menus, usually using the mouse, and feel frustrated and powerless for not being able to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry, then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. The descriptions should contain synonyms for commands; e.g. "insert picture" = "insert image" = "add picture".

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type here to invoke a command such as menu item to invoke".

[[Image:OO_command_bar_proposal.png|600px|Command bar mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.0, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement ==

Several places for putting the command (search) bar were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command bar next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command bar, just like a URL bar in a web browser. If the window gets too small, the bar may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command names can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search bar, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of command names of menu items</strike>
* Add synonymous names
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search

2008-11-28T01:45:25Z

Pgan002: /* Placement */

This is a design of a new, simple way to interact with OpenOffice applications. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus, users spend a lot of time and concentration manually searching the menus, usually using the mouse, and feel frustrated and powerless for not being able to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry, then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. The descriptions should contain synonyms for commands; e.g. "insert picture" = "insert image" = "add picture".

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type here to invoke a command such as menu item to invoke".

[[Image:OO_command_bar_proposal.png|600px|Command bar mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.0, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement ==

Several places for putting the command (search) bar were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# In place of the menu bar, when explicitly invoked (say under the Tools menu or by pressing F7). It would disappear when user presses Escape or executes a command.
# Next to the cursor or selected object, when explicitly invoked.

The consensus is to put the command bar next to the menu bar, except perhaps for the MacOS version. Consistency with Mac OS X and other programs is important if everything else is equal, but users are already familiar with a URL bar, which is somewhat similar. And next to the menu bar it would have some advantages:

# It is more discoverable than under a menu. Users rarely look under Help because before trying on their own may avoid the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.
# It is more inviting to use, so users are more likely to take advantage of it
# It is not associated with getting help. If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the menu location and the shortcut Alt+h) with the thought of getting help.

Next to the menu bar, space is free. Resizing the window would resize the command bar, just like a URL bar in a web browser. If the window gets too small, the bar may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

== Other details ==

Command descriptions can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search bar, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of command names of menu items</strike>
* Add synonymous names
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search

2008-11-28T01:25:57Z

Pgan002: /* To do */

This is a design of a new, simple way to interact with OpenOffice applications. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus, users spend a lot of time and concentration manually searching the menus, usually using the mouse, and feel frustrated and powerless for not being able to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry, then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. The descriptions should contain synonyms for commands; e.g. "insert picture" = "insert image" = "add picture".

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type here to invoke a command such as menu item to invoke".

[[Image:OO_command_bar_proposal.png|600px|Command bar mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.0, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement ==

Several places for putting the command (search) bar were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# Make it appear only when explicitly invoked, say under the Tools menu or by pressing F7
# Next to the cursor or selected object

The consensus is to put the command (search) bar next to the menu bar, except perhaps for the MacOS version. then it could replace the menu bar until it is dismissed by pressing Escape or a command is executed.

Consistency with Mac OS X is important if everything else is equal, but here are some advantages to putting the command bar next to the menu bar.

# In plain view it is definitely more discoverable than under any menu.
# It is more inviting to use, so users are more likely to get the liberating benefits it provides.
# If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even consciously knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the window location and the shortcut Alt+h) with the thought of getting help.

Users probably will not look under Help before making effort on their own. This often avoids the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.

Next to the menu bar it would look different than existing programs. But there is already a near precedent with the URL bar, which is perhaps more entrenched than MacOS's command bar in the Help menu. There are even tutorials on the Web about how to put their Firefox URL bar in the same row as their menu bar.

If the command bar is placed in the menu bar, it would be prominent, and so very accessible. It would also take up space that is free anyway. Resizing the window would resize the command bar, just like a URL bar in a web browser. If the window gets too small, the bar may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

But in the end, a even command bar in the Help menu would be a great improvement over not having one at all.

== Other details ==

Command descriptions can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search bar, showing the in-box label (grey) and a tool tip
* <strike>Compile a list of command names of menu items</strike>
* Add synonymous names
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Team

2008-11-25T11:56:20Z

Pgan002: /* Members of the User Experience Team */

{{User Experience}}
__NOTOC__
This is the list of our members who want to share some information about themselves. It extends the [http://ux.openoffice.org/servlets/ProjectMemberList Project Member List] which is necessary to administer the [http://ux.openoffice.org/ User Experience project] but does allow to add any personal note. Adding information to this list is suggested at the wiki page [[User Experience/Community/How To Join|How to Join]] the User Experience team.

If you would like to add some information, please allow me to give some remarks:
* The OpenOffice.org login name is the name which does also serve as you email address (''loginname''@openoffice.org).
* The comments may contain your motivation for joining the UX project.
* The special interest states your personal interest or special knowledge for OpenOffice.org UX. It may be interesting for both people outside the team and us to judge what knowledge we can provide and what is missing. Just add:
** OpenOffice.org (the complete OpenOffice.org office suite)
** one or more names of modules (Writer, Calc, Impress, Draw, Base, ...)
** other areas of interest (website, installer, ...)
* Please do not forget to add the date of your data's last update in the format YYYY-MM-DD. (This is an indicator for the up-to-dateness and helps us to directly contact people who may still in this list, but don't have any interest anymore. For us, its far easier than searching in the the Wiki page [http://wiki.services.openoffice.org/w/index.php?title=User_Experience/Team&action=history history]).

''Thank you very much!''

== Members of the User Experience Team ==

{| class="prettytable sortable" border="1"
|-
! Name and User Site
! OpenOffice.org Login Name
! [[IRC Communication|IRC]] Name
! Comments
! OpenOffice.org Special Interest
! Affiliation
! Blog
! Picture
! Last Update

|-
| [[User:Max13|Adnan RIHAN]]
| Max_13
| Max13
| WebMaster / WebDeveloper; Founder of an Open Source Association/Comunity; Student...
| -
| [http://www.virtual-info.wb.st/ = Virtual-Info =]
| -
| [[Image:Vinfologo_tiny.png]]
| (unknown)

|-
| [[User:Akashxavier|Akash Xavier]]
| akashxavier
| SingAlong
| Web Developer / User Interface Designer
| -
| [http://cafecamp.com Cafecamp.com]
| [http://jax.blogspot.com Jax's Blog]
| -
| -

|-
| [[User:juniorsplat|Alexander Pott]]
| Alexander Pott
| -
| Just a user
| -
| -
| -
| -
| (unknown)

|-
| [[User:wyrfel|André Wyrwa]]
| wyrfel
| wyrfel
| -
| -
| -
| [http://wyrfel.reukauf.com Wyrtual Life]
| -
| (unknown)

|-
| [[User:andba|Andreas Bartel]]
| andba
| andba
| User Experience Engineer
| -
| [http://www.sun.com/openoffice Sun Microsystems, Inc.]
| [http://ux.openoffice.org/blog/ OOo UX Blog]
| [[Image:AndreasBartel.jpg]]
| 2008-09-29

|-
| [[User:AndreasSchuderer|Andreas Schuderer]]
| anjoschu
| anjoschu
| Linguist, Interaction Designer
| -
| -
| [http://www.schuderer.net/experiments.shtml Live Mockups & Experiments]
| [[Image:Andreas_Schuderer.jpg]]
| (unknown)

|-
| [[User:cirano13|Arvind]]
| Arvind
|
| Student
| -
| -
| -
| -
| 2008-08-14

|-
| [[Bettina Haberer]]
| bh
| bettina_h
| User Experience Engineer
| -
| [http://www.sun.com/openoffice Sun Microsystems, Inc.]
| [http://ux.openoffice.org/blog/ OOo UX Blog]
| -
| 2008-07-27

|-
| [[User:CaioTiago|Caio Tiago Oliveira]]
| asrail
| asrail
| Computer Scientist / Accessibility lover
| -
| [http://broffice.org BrOffice.org]
| [http://my.opera.com/Asrail Asrail (mainly portuguese)]
| -
| (unknown)

|-
| [[User:Cj|Christian Jansen]]
| cj
| chris-j
| User Experience Engineer
| -
| [http://www.sun.com/openoffice Sun Microsystems, Inc.]
| [http://ux.openoffice.org/blog/ OOo UX Blog]
| -
| 2008-07-27

|-
| [[User:ChristophNoack|Christoph Noack]]
| christophnoack
| christoph_n
| Project co-lead [http://ux.openoffice.org OOo UX project]
| OpenOffice.org
| -
| [http://ux.openoffice.org/blog/ OOo UX Blog]
| [[Image:User_Christoph_Noack.png]]
| 2008-07-27

|-
| [[User:cornouws|Cor Nouws]]
| cornouws
| cornouws
| OpenOffice.org trainer OOo extensions developer
| -
| [http://www.nouenoff.nl Nou&Off (Dutch)]
| -
| -
| (unknown)

|-
| [[User:D_b|db email me for full name.]]
|Db.
|
| Student
| -
| -
| -
| -
| 2008-30-10

|-
| [[User:Abhar|F. Abhar]]
| Abhar
|
| Student, part-time Software Research Engineer
| -
| -
| -
| -
| 2008-07-28

|-
| [[User:frank_de_boer|Frank de Boer]]
| Frank_de_boer
| T1
| User Experience Engineer
| -
| -
| -
| http://home.versatel.nl/j.a.deboer/fotoschets.jpg
| (unknown)

|-
| [[User:Fl|Frank Loehmann]]
| fl
| frankl
| Project lead [http://ux.openoffice.org OOo UX project]
| -
| [http://www.sun.com/openoffice Sun Microsystems, Inc.]
| [http://ux.openoffice.org/blog/ OOo UX Blog]
| [[Image:Picture_FL.jpg]]
| 2008-07-27

|-
| [[User:digitalpractices|Garth A. Buchholz]]
| digitalpractices
| -
| Certified Usability Analyst (HFI), Internet researcher and User Experience Designer with expertise in government and corporate Web sites
| -
| [http://digitalpractices.com/ DigitalPractices Media Inc.]
| [http://digitalpractices.com/ DigitalPractices.com]
| [[Image:Dp-logo.jpg]]
| 2008-09-18

|-
| [[User:gleb|Gleb]]
| gleb
| -
| Just a user
| -
| -
| -
| -
| (unknown)

|-
| [http://www.brighton.ac.uk/centrim/graham Graham Perrin]
| grahamperrin
| grahamperrin
| interests include Access Grid, CalDAV and iCalendar, collaborative real-time editors, IRC, Jabber IM, MacFUSE, MacFusion, NeoOffice, OpenOffice.org and Plone
| Apple Mac OS X
| [http://www.brighton.ac.uk/centrim CENTRIM]
| http://cheekymonkey.bounceme.net/ usually leads to Diigo
| -
| 2008-11-18

|-
| [[User:Gawry|Gustavo Gawry]]
| gawry
| gawry
| User Experience Analyst
| -
| [http://www.sirius.com.br Sirius Interativa (portuguese)]
| [http://www.gawry.com Gawry (portuguese)]
| -
| (unknown)

|-
| [[User:JaronBaron|Jaron Kuppers]]
| JaronBaron
| -
| Mech. Eng., User, Supporter of Open Source Projects, Amateur UI designer
| -
| -
| -
| -
| (unknown)

|-
| [[User:Sryii|Joshua Horton]]
| Sryii
| Sryii
| Just a user, focused on use of OpenOffice.org for the scientific research
| -
| -
| -
| -
| (unknown)

|-
| [[User:discoleo|Leonard Mada]]
| -
| -
| Medical Doctor, Biomedical Informatics
| -
| -
| -
| -
| (unknown)

|-
| [[Lutz Hoeger]]
| lh
| lutzh
| Senior Product Manager Office Productivity Tools
| -
| [http://www.sun.com/openoffice Sun Microsystems, Inc.]
| [http://blogs.sun.com/GullFOSS/tags/user-experience GullFOSS]
| -
| (unknown)

|-
| [[User:ApOgEE|M. Fauzilkamil Zainuddin]]
| apogee
| ApOgEE-
| A User who is interested in having comfortable and end-user friendly free Office Suite for me and friends around me
| -
| [https://edge.launchpad.net/~apogee ApOgEE on Launchpad]
| [http://coderstalk.blogspot.com Coder's Talk Blog]
| [[Image:Gitar-192x192.jpg]]
| (unknown)

|-
| [[User:TokyoWitch|Maria Turk]]
| TokyoWitch
| TokyoWitch
| Artist, Interaction Designer
| -
| -
| -
| -
| (unknown)

|-
| [[User:josmar52789|Martin]]
| josmar52789
| -
| Web Developer / System Administrator
| -
| -
| -
| -
| (unknown)

|-
| [[User:Massoud|Massoud Toussi]]
| Massoud
|
| Medical Doctor, Biomedical Informatics; I love Open Source concept.
| -
| -
| [http://closeclinical.com]
| -
| (unknown)

|-
| [[User:wizard|Matthew Green]]
| wizard
|
| User; Long time user and lecturer to users of the ''other'' office suite (circa 1992)
| -
| -
| -
| -
| (unknown)

|-
| [[User:Mmp|Matthias Müller-Prove]]
| mmp
| mprove
| User Experience Architect (Sun Desktop Virtualization)
| -
| [http://www.sun.com/virtualization Sun Microsystems, Inc.]
| [http://uxooo.blogspot.com/ uxooo.blogspot.com]
| http://www.mprove.de/_media/mprove/mmp.jpg
| 1-Apr-2008

|-
| [[User:Ophilar|Ophilar]]
| Ophilar
| -
| User, Student, much in favour of FOSS and try to convert others
| -
| -
| -
| -
| (unknown)

|-
| [[User:praachee|Prachi Gupta]]
| PG
| -
| Software Engineer interested in making software more user friendly.
| -
| -
| -
| [[Image:Picture.jpg]]
| (unknown)

|-
| [[User:Rcsilva83|Rodrigo Carvalho]]
| Rcsilva83
| -
| User, developer and free software lover!
| -
| -
| [http://rcarvalho.wordpress.com/ http://rcarvalho.wordpress.com/]
| -
| (unknown)

|-
| [[User:seijideasign|Sébastien JUST]]
| seijideasign
| seijideasign
| IT Manager with expertise in end-user behavior
| Writer, Calc and Draw ergonomics and productivity improvement
| [http://www.seij.net seijideasign Web Site]
| [http://seijideasign.blogspot.com/ seijideasign Blog]
| -
| 2008-11-15

|-
| [[User:Sbw99|Sean Brady]]
| sbw99
| -
| UX professional offers expertise in agile usability testing, ethnographic research, interaction design
| -
| -
| -
|
| 2008-09-04

|-
| [[User:Tereno|Teren Teh]]
| Tereno
| Tereno
| Student interested in User Experience and HCI
| -
| -
| -
| -
| 2008-11-21

|-
| [[User:TheGurkha|TheGurkha]]
| TheGurkha
|
| User; long-time software professional, I manage a development team.
| -
| -
| -
| -
| 2008-08-29

|-
| [[User:ajpursell|Tony Pursell]]
| ajpursell
| -
| User
| -
| -
| -
| -
| (unknown)

|-
| [[User:Trisi|Trisilav]]
| Trisilav
| Trisilav
| Student, and independent ui designer, member of the OpenOffice.org Art team
| -
| -
| -
| -
| (unknown)

|-
| [[User:Vincent_Rappa|Vincent Rappa]]
| Vincent Rappa
| Hawkskater
| Ubuntu fan trying to improve open source applications
| -
| -
| -
| -
| (unknown)

|-
| [[User:Dz0|Vincent Rappa]]
| Dz0
| -
| User; I want to have comfortable free office suite (for oneself and others), and I try to promote it (especially in education)
| -
| [http://akl.lt/en Open Source for Lithuania]
| -
| -
| (unknown)

|-
| [[User:Pgan002|Philip Ganchev]]
| Pgan002
| Pgan, Pgan002
| 
| 
| 
| 
| 
| 2008-11-25

|}

You want to be part of the User Experience Team? Then please refer to [[User Experience/Community/How To Join|How to Join]].

== Related Pages ==
* [[DomainDeveloper]]
* [http://ux.openoffice.org/servlets/ProjectMemberList ux.openoffice.org project member list]

[[Category:User Experience|Community]]

User:Pgan002

2008-11-25T11:42:38Z

Pgan002: New page: {{User Experience Community}}

User Experience/Command search

2008-11-24T23:58:07Z

Pgan002: /* Placement */

This is a design of a new, simple way to interact with OpenOffice applications. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus, users spend a lot of time and concentration manually searching the menus, usually using the mouse, and feel frustrated and powerless for not being able to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry, then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. The descriptions should contain synonyms for commands; e.g. "insert picture" = "insert image" = "add picture".

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type here to invoke a command such as menu item to invoke".

[[Image:OO_command_bar_proposal.png|600px|Command bar mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.0, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement ==

Several places for putting the command (search) bar were discussed on the UX mailing list:
# Next to the window's menu bar
# As an entry in the "Help" menu, as in some Mac OS X applications ([http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218 illustration])
# Make it appear only when explicitly invoked, say under the Tools menu or by pressing F7
# Next to the cursor or selected object

The consensus is to put the command (search) bar next to the menu bar, except perhaps for the MacOS version. then it could replace the menu bar until it is dismissed by pressing Escape or a command is executed.

Consistency with Mac OS X is important if everything else is equal, but here are some advantages to putting the command bar next to the menu bar.

# In plain view it is definitely more discoverable than under any menu.
# It is more inviting to use, so users are more likely to get the liberating benefits it provides.
# If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even consciously knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the window location and the shortcut Alt+h) with the thought of getting help.

Users probably will not look under Help before making effort on their own. This often avoids the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.

Next to the menu bar it would look different than existing programs. But there is already a near precedent with the URL bar, which is perhaps more entrenched than MacOS's command bar in the Help menu. There are even tutorials on the Web about how to put their Firefox URL bar in the same row as their menu bar.

If the command bar is placed in the menu bar, it would be prominent, and so very accessible. It would also take up space that is free anyway. Resizing the window would resize the command bar, just like a URL bar in a web browser. If the window gets too small, the bar may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

But in the end, a even command bar in the Help menu would be a great improvement over not having one at all.

== Other details ==

Command descriptions can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search bar, showing the in-box label (grey) and a tool tip
* Compile a list of command names of menu items
* Add synonymous names
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search

2008-11-24T23:45:16Z

Pgan002: /* Menu entries */

This is a design of a new, simple way to interact with OpenOffice applications. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus, users spend a lot of time and concentration manually searching the menus, usually using the mouse, and feel frustrated and powerless for not being able to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry, then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. The descriptions should contain synonyms for commands; e.g. "insert picture" = "insert image" = "add picture".

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type here to invoke a command such as menu item to invoke".

[[Image:OO_command_bar_proposal.png|600px|Command bar mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.0, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement ==

The consensus on the UX mailing list is to put the command (search) bar next to the menu bar, except perhaps for the MacOS version. There was discussion about putting it under the "Help" menu. It can also appear only when explicitly invoked, say under the Tools menu or by pressing F7; then it could replace the menu bar until it is dismissed by pressing Escape or a command is executed.

Putting the search box inside the Help menu would be more consistent with MacOS X's command search - see [http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218]. Consistency is important if everything else is equal, but here are some advantages to putting the command bar next to the menu bar.

# In plain view it is definitely more discoverable than under any menu.
# It is more inviting to use, so users are more likely to get the liberating benefits it provides.
# If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even consciously knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the window location and the shortcut Alt+h) with the thought of getting help.

Users probably will not look under Help before making effort on their own. This often avoids the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.

Next to the menu bar it would look different than existing programs. But there is already a near precedent with the URL bar, which is perhaps more entrenched than MacOS's command bar in the Help menu. There are even tutorials on the Web about how to put their Firefox URL bar in the same row as their menu bar.

If the command bar is placed in the menu bar, it would be prominent, and so very accessible. It would also take up space that is free anyway. Resizing the window would resize the command bar, just like a URL bar in a web browser. If the window gets too small, the bar may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

But in the end, a even command bar in the Help menu would be a great improvement over not having one at all.

== Other details ==

Command descriptions can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== List of menu entries and buttons ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search bar, showing the in-box label (grey) and a tool tip
* Compile a list of command names of menu items
* Add synonymous names
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

User Experience/Command search

2008-11-24T23:35:53Z

Pgan002:

This is a design of a new, simple way to interact with OpenOffice applications. It is being discussed at the UX mailing list, [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=2124105 here]

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus, users spend a lot of time and concentration manually searching the menus, usually using the mouse, and feel frustrated and powerless for not being able to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry, then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. The descriptions should contain synonyms for commands; e.g. "insert picture" = "insert image" = "add picture".

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type here to invoke a command such as menu item to invoke".

[[Image:OO_command_bar_proposal.png|600px|Command bar mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.0, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement ==

The consensus on the UX mailing list is to put the command (search) bar next to the menu bar, except perhaps for the MacOS version. There was discussion about putting it under the "Help" menu. It can also appear only when explicitly invoked, say under the Tools menu or by pressing F7; then it could replace the menu bar until it is dismissed by pressing Escape or a command is executed.

Putting the search box inside the Help menu would be more consistent with MacOS X's command search - see [http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218]. Consistency is important if everything else is equal, but here are some advantages to putting the command bar next to the menu bar.

# In plain view it is definitely more discoverable than under any menu.
# It is more inviting to use, so users are more likely to get the liberating benefits it provides.
# If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even consciously knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the window location and the shortcut Alt+h) with the thought of getting help.

Users probably will not look under Help before making effort on their own. This often avoids the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.

Next to the menu bar it would look different than existing programs. But there is already a near precedent with the URL bar, which is perhaps more entrenched than MacOS's command bar in the Help menu. There are even tutorials on the Web about how to put their Firefox URL bar in the same row as their menu bar.

If the command bar is placed in the menu bar, it would be prominent, and so very accessible. It would also take up space that is free anyway. Resizing the window would resize the command bar, just like a URL bar in a web browser. If the window gets too small, the bar may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

But in the end, a even command bar in the Help menu would be a great improvement over not having one at all.

== Other details ==

Command descriptions can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

[[Image:Command_search_revealinmenu.png|thumb|Mockup for providing an icon to reveal the command's position in the application menu structure.]]
There may be an option to reveal a command's corresponding position in the menu, e.g. an icon ("reveal in menu"), positioned at the right edge of the results list.

== Menu entries ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search bar, showing the in-box label (grey) and a tool tip
* Compile a list of command names of menu items
* Add synonymous names
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]

Help Agent

2008-11-24T03:19:24Z

Pgan002: /* Possible Solutions */

[[Category:User Experience]]
[[Category:Documentation/OnlineHelp]]
The Help Agent is a small window that opens automatically in the lower right corner of the OOo document window. It generally shows an image of a light bulb.

A list of events that call the Help Agent is defined in the file SFX.xcu in the directory
share/registry/data/org/openoffice/Office. This file is not part of the helpcontent2 module.

There is a request for enhancement to remove the Help Agent. See http://www.openoffice.org/issues/show_bug.cgi?id=53114

== Why the Help Agent is bad ==

=== People don't tend to read the hints ===

Usability research revealed this typical user behaviour pattern:

1. A user writes some text in Writer, starting with a lower case letter.

2. The automatic AutoCorrect feature converts the lower case character to upper case.

3. This is one of the events that trigger the Help Agent, which now shows in the lower right corner.

4. User tells "What the heck happened here? It converted my character. How can I get rid of this automatism?"

5. At the same time the user clicks away the Help Agent.

The Help Agent, when clicked in the window, would just have answered the user's questions. But the user closed it.

=== Others ===

* Because it is a popup window, it is annoying.

* It also brings back bad memories of the animated paperclip in Microsoft Word 97 and 2000.

== How to disable ==

You can permanently disable the Help Agent on the ''Tools - Options - OOo - General'' dialog. The Help Agent is disabled automatically for a certain event when you close it or don't pay notice three consecutive times for this event. The list of events for which the Help Agent will no more show up automatically can be reset on the same dialog page.

== Possible Solutions ==

Have a more intelligent Help Agent:

* it would show up only when the help text is really helpful,

* there should be no complicated paths to dialog boxes where you can manually enable/disable features, but the Help Agent itself would include buttons to enable/disable a feature.

Replace Help Agent by smart popup dialogs. (What's the benefit of this? It annoys users even more and they still don't read the message.)

Show the actual help message text (or the start of it, if it is too long), instead of the help agent icon. That way the user does not have to interact with the agent to know what happened, and is more likely to read the message.

== External links ==

* [http://ux.openoffice.org/issues/show_bug.cgi?id=62204 bug 62204], "ux-ctest: Appearance of Help agent astonished user."
* [http://www.openoffice.org/issues/show_bug.cgi?id=74677 bug 74677], "Help Agent should only pop up once per tip"
* [http://www.openoffice.org/issues/show_bug.cgi?id=74678 bug 74678], "Help Agent should be shrunk and only appear in statusbar, so as to distract users less"
* [http://www.openoffice.org/issues/show_bug.cgi?id=74679 bug 74679], "Help Agent should not trigger when the user types a quotation mark (") in Writer."
* [http://wiki.services.openoffice.org/wiki/FeatureSuggestions#Help_Agent_Notification Help Agent Notification] - GNOME notification area suggestion

* [http://specs.openoffice.org/appwide/menus/HelpMenu.sxw Help Agent specification] - includes user scenarios, goals, diagrams, etc. (.sxw format)

Mail list discussions:

http://www.openoffice.org/servlets/ReadMsg?listName=discuss&msgNo=57241

http://www.openoffice.org/servlets/ReadMsg?listName=discuss&msgNo=59619

Help Agent

2008-11-24T03:18:56Z

Pgan002: /* Possible Solutions */ one more solution

[[Category:User Experience]]
[[Category:Documentation/OnlineHelp]]
The Help Agent is a small window that opens automatically in the lower right corner of the OOo document window. It generally shows an image of a light bulb.

A list of events that call the Help Agent is defined in the file SFX.xcu in the directory
share/registry/data/org/openoffice/Office. This file is not part of the helpcontent2 module.

There is a request for enhancement to remove the Help Agent. See http://www.openoffice.org/issues/show_bug.cgi?id=53114

== Why the Help Agent is bad ==

=== People don't tend to read the hints ===

Usability research revealed this typical user behaviour pattern:

1. A user writes some text in Writer, starting with a lower case letter.

2. The automatic AutoCorrect feature converts the lower case character to upper case.

3. This is one of the events that trigger the Help Agent, which now shows in the lower right corner.

4. User tells "What the heck happened here? It converted my character. How can I get rid of this automatism?"

5. At the same time the user clicks away the Help Agent.

The Help Agent, when clicked in the window, would just have answered the user's questions. But the user closed it.

=== Others ===

* Because it is a popup window, it is annoying.

* It also brings back bad memories of the animated paperclip in Microsoft Word 97 and 2000.

== How to disable ==

You can permanently disable the Help Agent on the ''Tools - Options - OOo - General'' dialog. The Help Agent is disabled automatically for a certain event when you close it or don't pay notice three consecutive times for this event. The list of events for which the Help Agent will no more show up automatically can be reset on the same dialog page.

== Possible Solutions ==

Have a more intelligent Help Agent:

* it would show up only when the help text is really helpful,

* there should be no complicated paths to dialog boxes where you can manually enable/disable features, but the Help Agent itself would include buttons to enable/disable a feature.

* Replace Help Agent by smart popup dialogs. (What's the benefit of this? It annoys users even more and they still don't read the message.)

* Show the actual help message text (or the start of it, if it is too long), instead of the help agent icon. That way the user does not have to interact with the agent to know what happened, and is more likely to read the message.

== External links ==

* [http://ux.openoffice.org/issues/show_bug.cgi?id=62204 bug 62204], "ux-ctest: Appearance of Help agent astonished user."
* [http://www.openoffice.org/issues/show_bug.cgi?id=74677 bug 74677], "Help Agent should only pop up once per tip"
* [http://www.openoffice.org/issues/show_bug.cgi?id=74678 bug 74678], "Help Agent should be shrunk and only appear in statusbar, so as to distract users less"
* [http://www.openoffice.org/issues/show_bug.cgi?id=74679 bug 74679], "Help Agent should not trigger when the user types a quotation mark (") in Writer."
* [http://wiki.services.openoffice.org/wiki/FeatureSuggestions#Help_Agent_Notification Help Agent Notification] - GNOME notification area suggestion

* [http://specs.openoffice.org/appwide/menus/HelpMenu.sxw Help Agent specification] - includes user scenarios, goals, diagrams, etc. (.sxw format)

Mail list discussions:

http://www.openoffice.org/servlets/ReadMsg?listName=discuss&msgNo=57241

http://www.openoffice.org/servlets/ReadMsg?listName=discuss&msgNo=59619

Platform UI Differences

2008-11-24T03:02:00Z

Pgan002: /* Differences */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]

==Introduction==
While the [[UI Layout]]-page shows the conceptual differences between the platforms, it is not possible to create good UI by just high-level changes. This page aims to document the differences in details in the UI (and report the status in Ooo).

Since the current OOo is more-or-less carbon copy of Windows XP GUI on '''all''' platforms, this page will not document that GUI at all. Focus is put to the platforms that differ from Windows XP GUI.

==Complementary and Related projects==

The possible future UI Layout work is complementary and not overlapping with:
* [http://indiehig.com/wiki/Main_Page Indie HIG] The Missing manuals on the Mac OS X User Interface
* Graphics Rendering re-work: [[Mac_OS_X_Porting_-_Canvas|OOo Canvas]]
* [[Uno/Effort/Uno_Runtime_Environment|UNO Runtime environment]]
* [http://odftoolkit.openoffice.org/ ODF Toolkit] and
* OOo Runner [[Mac_OS_X_Porting_-_Separate_apps_%28OOoRunner_-framework%29|Separate Apps on Mac OS X]]
* [http://library.gnome.org/devel/hig-book/stable/ Gnome Human Interface Guidelines] for Solaris and Linux Gnome Desktops (the XFCE Desktop follows these guidelines too most of the time)

==Goals==

Document the differences in Platform specific UIs (e.g. Aqua/Mac OS X, Aero/Vista, Gnome/Linux, KDE/Linux Win32/Windows XP).

Follow the implementation progress with status-tables.

The focus is in stuff expressed in GUI guidelines (e.g. Aqua HIG, Aero xxx, Gnome UI SG,...) and stuff that is ''standard'' or ''preferred'' way of doing things, as exemplified by high quality applications on each platform (e.g. Apple Pages (iWork) on Mac OS X, MS Word (Vista Office), and Abiword on Gnome)

==Differences==

The following lists and documents the differences in the typical applications used on various platforms, compared to OpenOffice.org. The aim is to show that while there are similarities in these platform-specific applications, and much of the actual functionality is quite similar, the actual UI (i.e. '''how''' you accomplish those functions) has differences both on surface and in deeper levels.

Stuff to add (Mac OS X):
* OK/cancel buttons: ok on the right side (this is also true for Gnome/XFCE on Linux/Solaris, KDE supports both but defaults to the Win32 way)
* The "jellybean" button that hides the toolbar
* Blend the toolbar background with the menu bar

{| border="1" cellpadding="5" cellspacing="0" align="center"
|+'''Platform specific UI differences'''
|-
! style="width:100px;" |   !! style="background:#59e;width:210px;" | Mac OS X (Aqua) !! style="background:#59e;width:210px;" | Windows Vista (Aero) !! style="background:#59e;width:210px;" | Ubuntu Linux/Sun Java Desktop for Solaris (Gnome)
|-
! style="background:#abcdef;" colspan="4" | Application Menu
|-
| '''Location''' ''Where the menu is located''
|| [[Image:Aqua-menu.png]] System wide menu in the top of the screen. Contents of the menu depend on which is the active window
|| [[Image:Vistaoffice-menu.png]] '''Vista Office''' (Ribbon UI): Merging of menus and toolbars, resulting in tabbed toolbars. '''Vista''' (Aero): In the top of the application window.
|| In the top of the application window
|-
| '''Icons'''
|| [[Image:Aqua-menu-no-icons.png]] No icons in the menu || '''Ribbon:''' No (regular) menus. '''Aero:''' No icons in the menu || typically icons in the menu (system option)
|-
| '''Main structure''' ''what are the top-level menu items'' || Apple-button (systemwide), Pages (i.e. the application menu), File, Edit, Insert, Format, Arrange, View, Window, Help. In total: 10 || '''Ribbon/Word:''' Office-button (similar to "File" -menu), Home, Insert, Page Layout, References, Mailings, Review, View. In total: 8. ''Note: Clearly task-oriented structure'' || File, Edit, View, Insert, Format, Bookmarks, Go, Windows, Help see [http://library.gnome.org/devel/hig-book/stable/menus-standard.html.en HIG about standard menus]
|-
| '''Preferences''' ''Where the settings are located and what they are called'' || [[Image:Aqua-menu-preferences.png]] '''Preferences...''' in the "'''Application menu'''" e.g. Pages -menu, accessible with CMD-, || '''Options...''' in Tools -menu?? || '''Preferences''' as last entry in the Editmenu
|-
! style="background:#abcdef;" colspan="4" | Toolbars
|-
| '''Icons''' ''The default setting'' || [[Image:Aqua-toolbar-tn.png]] [http://mox.fidisk.fi/opensource/UI/differences/aqua-toolbar.png full size] 10-15 icons (large: 30x30px) with text underneath || [[Image:Vistaoffice-toolbar-tn.png]] [http://mox.fidisk.fi/opensource/UI/differences/vistaoffice-toolbar.png full size] '''Ribbon:''' three sizes. Amounts per tab - ''Main actions:'' 3-11 icons, (large: 35x35px) with text underneath. ''Important actions:'' 3-19 icons, (small: 20x20px) with text on the right side. ''Other actions:'' 0-29 icons, (small: 20x20px) without text. || 10-15 icons (size: 24x24px, 48x48 option for accessability) with text underneath as default. Text only or icon only are available as options
|-
| '''Customization''' ''How the toolbars are customized'' || [[Image:Aqua-toolbar-customize-tn.png]] [http://mox.fidisk.fi/opensource/UI/differences/aqua-toolbar-customize.png full size] Main toolbars are customizable through right clicking, selecting '''Customize...''' and then drag-and-dropping. ''Much of the toolbar functionality in'' '''Inspector''' ''-tool instead.'' || [[Image:Vistaoffice-toolbar-customize-tn.png]] [http://mox.fidisk.fi/opensource/UI/differences/vistaoffice-toolbar-customize.png full size] '''Ribbon:''' Main toolbars are NOT customizable. The Quicklaunch toolbar is customisable from its toolbar and from "Customize" in ??? > Options -menu. Shows a dialog. || Not editable / occasionally the same style as Mac OS X. ''NOTE: Also in Mozilla applications''
|-
| '''Style''' ''What the toolbar icons/buttons look like'' || '''No surrounding 3D "button" around the icon''', colors used sparingly, as few metaphors as possible. Icons have subtle shadow. || ??? || No button borders, richer colors, icons in 3D perspective
|-
| '''Highlight''' ''What the toolbar icons/buttons look like, when clicked'' || '''No highlight''' ''No visual change in the button'' || '''Light-bulb highlight''' ''buttons look like they are shining'' || Highlights with dark color to show the full button area
|-
! style="background:#abcdef;" colspan="4" | Dialogs (and Sheets)
|-
| '''Customize Toolbar''' ''What kind of UI is used?'' || Opens a '''Sheet''' || Opens a '''Dialog''' || N/A or Opens a '''Sheet'''
|-
! style="background:#abcdef;" colspan="4" | Workflow (Task vs. other)
|-
! style="background:#abcdef;" colspan="4" | Interaction styles
|-
! style="background:#abcdef;" colspan="4" | Design goals
|-
| '''Target users''' ''What kind of people are the applications designing for?'' || Normal people who want to make well designed documents with good layout. '''Not just word processing'''
|| Word processing for the average Joe, lots of functionality
|| Usability important, clean UI
|-
| '''Templates''' ''What is the purpose of the templates?'' || To learn/get ideas for good style/design, '''professional quality''' || To have all the templates for all the possible occasions || Get the templates you want from the internet repositories
|-
|}

[[Category:Porting]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Architecture]]
[[Category:Features]]
[[Category:User Experience]]
[[Category:To-Do]]

Mac OS X Porting - Canvas

2008-11-24T02:46:05Z

Pgan002: /* Introduction */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]
* Thorsten Behrens (thb)

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]]. Another big problem of VCL is that also the internals of the VCL are used from many places in the OOo code.

The future rendering framework in OOo is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a better designed API (easier to port and use) and a stronger isolation of the API from the rest of OOo.

Currently, the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:Oocon2006_g11-drawinglayer.png|right|500px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OOo, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

Now there are cairo-based Canvas backends for Unix/X11, Windows and Mac/Quartz. The text rendering, however, is always directed back to VCL. To take the full advantage of cairo library, and it's support for cross-platform text layout and rendering, the [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvasFont.html XCanvasFont] and [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XTextLayout.html XTextLayout] interfaces need to be implemented "natively" with cairo.

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=88613 issue 88613])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-11-24T02:45:42Z

Pgan002: /* Introduction */ larger image

==Contributors==
* Mox Soini: [[User:Mox|Mox]]
* Thorsten Behrens (thb)

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]]. Another big problem of VCL is that also the internals of the VCL are used from many places in the OOo code.

The future rendering framework in OOo is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a better designed API (easier to port and use) and a stronger isolation of the API from the rest of OOo.

Currently, the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:Oocon2006_g11-drawinglayer.png|left|500px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OOo, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

Now there are cairo-based Canvas backends for Unix/X11, Windows and Mac/Quartz. The text rendering, however, is always directed back to VCL. To take the full advantage of cairo library, and it's support for cross-platform text layout and rendering, the [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvasFont.html XCanvasFont] and [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XTextLayout.html XTextLayout] interfaces need to be implemented "natively" with cairo.

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=88613 issue 88613])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-11-24T02:43:16Z

Pgan002: /* Introduction */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]
* Thorsten Behrens (thb)

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]]. Another big problem of VCL is that also the internals of the VCL are used from many places in the OOo code.

The future rendering framework in OOo is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a better designed API (easier to port and use) and a stronger isolation of the API from the rest of OOo.

Currently, the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|500px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OOo, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

Now there are cairo-based Canvas backends for Unix/X11, Windows and Mac/Quartz. The text rendering, however, is always directed back to VCL. To take the full advantage of cairo library, and it's support for cross-platform text layout and rendering, the [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvasFont.html XCanvasFont] and [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XTextLayout.html XTextLayout] interfaces need to be implemented "natively" with cairo.

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=88613 issue 88613])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Mac OS X Porting - Canvas

2008-11-24T02:42:25Z

Pgan002: /* Introduction */

==Contributors==
* Mox Soini: [[User:Mox|Mox]]
* Thorsten Behrens (thb)

==Introduction==
The current rendering framework in OpenOffice.org (OOo) is VCL. It is very Windows-oriented API that is hard to port to other platforms. Despite this, there are several ports available, including Unix/X11, Windows and [[AquaBuild|Native Mac OS X port using Cocoa]]. Another big problem of VCL is that also the internals of the VCL are used from many places in the OOo code.

The future rendering framework in OOo is [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html UNO XCanvas rendering framework]. The benefits include a better designed API (easier to port and use) and a stronger isolation of the API from the rest of OOo.

Currently, the XCanvas implementation has been jump-started by directing text rendering back to VCL.

[[Image:oocon2006_g11-drawinglayer-thumb.png|left|200px|The location of the Drawing layer. Click on image for full view]]

XCanvas is part of bigger module in OOo, called ''Drawing Layer''. There is initiative to improve the whole module: [[DrawingPrimitives|Drawing Layer/Drawing Primitives]]

For '''XCanvas information''', see presentations at [http://marketing.openoffice.org/ooocon2006/schedule/wednesday.html OOoCon 2006] (PDF, ODP, video/ogg) and [http://ooocon-arnes.kiberpipa.org/media/Cairo_Radek_Doulik/slide.pdf OOoCon 2005 (PDF)]

Of the OOo applications using VCL, currently (September 2006) OOo Impress slideshow [http://marketing.openoffice.org/ooocon2006/schedule/general_abstracts.html#g11 has been converted to XCanvas], with prototypes working in Draw and Impress. Future work will include converting Calc and Writer.

NOTE: this work does not address the problem with native widgets and UI layout, only rendering. The UI Layout is discussed in [[UI Layout]] and details are in [[VCL UI Rework]].

==Roadmap for Canvas in Mac OS X==

'''Short term:''' use the VCL implementation of XCanvas.

'''Long term:''' create a native implementation of XCanvas. There are two alternative ways to complete this:

# Create complete, non-VCL, canvas implementation in OOo (like the Windows implementation, not worked on in Mac OS X)
# Create implementation based on [http://www.cairographics.org Cairo -library] (like the Linux implementation, this is the currently chosen alternative for Mac OS X)

The benefits of cairo-based implementation include:
* Less code in OOo, more shared code with other open source programs
* Cairo has been already ported to Mac OS X, no need to duplicate that effort for OOo only.
* [http://www.mozilla.org Mozilla] is using this approach (in Gecko 1.9 / Firefox 3.0) for all of their platforms (The [http://wiki.mozilla.org/Mozilla2:GFXEvolution Thebes API], which is a light C++ API on top of Cairo API in C)
* [http://www.gtk.org GTK/Gnome] is using this approach for all of their platforms (The new Canvas-widget & rendering, based on Cairo)

==Status==

As of Apr 2008, the Quartz cairo canvas for OOo Mac OS X is implemented, but not fully working. All the text is not visible, although actual rendering works ok. There's also a crash when closing down Canvas.

DONE:
* Cairo canvas code documentation added
* Quartz backend added to Cairo Canvas ([http://www.openoffice.org/issues/show_bug.cgi?id=69066 issue 69066])

==Tasks==

Now there are cairo-based Canvas backends for Unix/X11, Windows and Mac/Quartz. The text rendering, however, is always directed back to VCL. To take the full advantage of cairo library, and it's support for cross-platform text layout and rendering, the [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvasFont.html XCanvasFont] and [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XTextLayout.html XTextLayout] interfaces need to be implemented "natively" with cairo.

TODO:
* Create cross-platform cairo-based text rendering for cairo canvas backend ([http://www.openoffice.org/issues/show_bug.cgi?id=88613 issue 88613])

==Links==

* [http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua/Mac OS X related Wiki pages]
* Related work: The re-design of [[DrawingPrimitives|Drawing layer in Impress/Draw]], to make it possible to use XCanvas in Impress and Draw
* OpenOffice.org [[Architecture]]
* Quartz 2D: [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ context explained], [http://developer.apple.com/documentation/GraphicsImaging/Reference/CGImage/Reference/reference.html#//apple_ref/c/func/CGImageCreateWithMask Image Masks], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/dq_images/chapter_12_section_1.html#//apple_ref/doc/uid/TP30001066-CH212 Mask explanation]
* [http://developer.apple.com/documentation/GraphicsImaging/Reference/Quartz2D_Collection/index.html#//apple_ref/doc/uid/TP40003853 Linked list of Quartz 2D functions]

The APIs that are involved are ([http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas], [http://www.cairographics.org/manual/cairo-Image-Surfaces.html Cairo], [http://developer.apple.com/documentation/GraphicsImaging/Conceptual/drawingwithquartz2d/ Quartz 2D], and a little bit of [http://developer.apple.com/cocoa/ Cocoa])

[[Category:Porting]]
[[Category:MacOSX]]
[[Category:Aqua]]
[[Category:Development]]
[[Category:Features]]

Smart Tags Interaction

2008-11-24T02:36:34Z

Pgan002: /* Specification */

{{User Experience}}
By Frank Loehmann, User Experience Engineer at Sun Microsystems

=User Interaction with Smart Tags=

The term "Smart Tags" is used synonymously for many different things. RFID-Tags/Labels (i.e. to label goods in stores) are often called "Smart Tags" too. In software products the term Smart Tag is used for content and action driven Smart Tags. OOo has already implemented the content driven [[Smart_Tags|Smart Tags with OOo 2.2]] and will offer a final API and UI with OOo 2.3. Action driven Smart Tags are planned for the future, so we have to consider those when designing the UI for content driven sart tags.

In the following I will create a list of related functions and UI of OOo.

=Related Areas=

* AutoCorrection
* Online spelling (spell while you type)
* content driven smart tags
* action driven smart tags
* help agent (the icon in the lower right corner of the application)

All these are content or action driven Smart Tags.

=Specification=

Please find details about the specification in the following specification [http://specs.openoffice.org/appwide/SmartTags/Smart_Tags_Specification.odt].

User Experience/ToDo/Competitor Software

2008-11-24T02:29:42Z

Pgan002: /* Responsiveness */

{{User Experience}}

The aim of this page is to provide an '''analysis''' of useful features from competitor software. Competing software includes:

* Adobe InDesign CS3
* Adobe Acrobat Professional
* Apple iWorks
* Microsoft Office
* IBM Lotus Symphony
* various web-pages
* specific controls:
** Adobe Type Manager: group fonts
* ... please expand

== Table Styles ==

Virtually every table on the net uses the following specific design:

=== Design ===
* '''header row:''' a background color is set
* '''table-rows:'''
** two alternating backgrounds
** usually NO hard-borders, but usually light borders
* highlight current row: interactive programs (aka web) implement this feature, too
* slightly rounded corners: sometimes a pretty cheap but visually pleasing effect

=== Competitor Software ===
* virtually every web table, including the '''[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=FEATURE&issue_status=NEW OOo]''' and [http://crash-stats.mozilla.com/topcrasher/byversion/SeaMonkey/2.0a1pre Mozilla] issue-lists use these web-proven designs.
* Adobe InDesign CS3:
** [http://www.adobe.com/products/indesign/features/allfeatures Be more productive] -> ''Full featured tables'' paragraph:
** [http://www.adobe.com/products/indesign/features/ flash demo:] see the whole demo

=== Usability ===
* Writer: implement such a table style (NO issue yet filed)
* Calc: implement a ''Spreadsheet''-'''Table View''', see [http://www.openoffice.org/issues/show_bug.cgi?id=78181 issue 78181]
** including different header style, alternating background for data-rows and highlight current row
* Impress: '''highlight''' current row/ current area, see [http://www.openoffice.org/issues/show_bug.cgi?id=79882 issue 79882]

== Styles & Themes ==
* iWork: professional looking styles & themes out of the box
* MS Office 2007: also professional looking styles & themes out of the box
** Using these two products you have to almost struggle to create ugly documents
** No confusion caused by multiple simultaneous pragmas (strong manual editing support vs styles based)
** Themes format styles automatically, which means extremely easy switching of the whole look
* OOo is very poor on this area!

== Side-by-Side Difference between 2 Documents ==

Many web-programs allow displaying side-by-side differences for 2 text-streams.

=== Design ===
* compute differences between 2 versions of a document (or even 2 completely different documents)
* choose difference-sensitivity: text-only, other-objects, formats, ...
* display the 2 pages side-by-side, when [http://www.openoffice.org/issues/show_bug.cgi?id=1598 issue 1598] gets implemented.

=== Competitor Software ===
* Adobe Acrobat Professional implements this feature
** it does a great job (including +/- formatting), even though pdf is such a poor format when it comes to page structure
* various web-programs/diff's: including mediawiki/wikipedia and many more
* various text-editors
* the BLAST-program: see [http://www.ncbi.nlm.nih.gov/BLAST/bl2seq/wblast2.cgi the ncbi BLAST page]

=== Usability ===
See [http://www.openoffice.org/issues/show_bug.cgi?id=81526 issue 81526] for further details.

== Context sensitivity ==
* Two types of controls (toolbar or anything else): fixed, which always have the same options; and dynamic, which, depending on the current context, shows different options (like Symphony's side-panel)
* Microsoft Office 2007 introduces a contextual spell checker.

== Toolbars and tool dialogs ==

=== Inspector (Apple iWork) ===
Apple's iWork has a concept of "Inspector", which is context sensitive, but with static set of tabs/controls.

It's not a toolbar, but a [https://www.apple.com/iwork/pages/features/processing.html floating window with tabs]. See [http://movies.apple.com/movies/us/apple/mac/iwork/2007/pages/iwork_pages_formattingadocument_20070807_640x360.mov formatting document movie] (Quicktime)

So for example you can select one or more graphical shapes (and tex boxes) and set from the inspector their X/Y position on page or their width and height. Also colors for any object (border/fill) can be changed etc.

=== Contextual Format Bar (Apple iWork) ===
If more toolbar-like UI is desired, then there's [http://movies.apple.com/movies/us/apple/mac/iwork/2007/features/iwork_features_contextualformatbar_20070807_r640-10cie.mov Contextual Format Bar] (Quicktime)

=== Extension Manager ===
Firefox 3's extension manager has a search box, so the user can search and install a extension direct for the program. This is very easy to use and very productive.

== Responsiveness ==
OOo programs respond slowly compared to MS Office. This includes scrolling, saving, focusing objects such as images and tables (due to changing of the tool bar), opening object settings dialogs, closing dialogs. The slow response times quite frustrate users.

[[Category:User Experience|To-Do/Competitor Software]]
[[Category:To-Do|Usability]]

User Experience/Command search

2008-11-23T10:03:31Z

Pgan002: /* To do */

This is a design of a new and simple way to interact with OpenOffice applications.

A major difficulty in using large applications like OpenOffice is that users do not know where to find the menu item or button they need, because there are so many menu items and buttons. Despite designer's efforts to organize the menus, users spend a lot of time and concentration manually searching the menus, usually using the mouse, and feel frustrated and powerless for not being able to achieve what they need.

It is more efficient for the computer to search for the menu items, based on query text entered by the user. The user types what she wants to do, and sees matching commands appear in a drop-down box under the query box. The list of matches shrinks as the user types. The user can hit Enter to activate the first entry, or use the arrow keys to select another entry, then press Enter.

The query matches substrings of command descriptions. If a query contains multiple words, they are matched as a conjunction (not as a string) of non-overlapping words. The descriptions should contain synonyms for commands; e.g. "insert picture" = "insert image" = "add picture".

The search box can appear next to the menu bar, right-aligned. It should be labeled "Type what you want to do (F7)" or similar inside the box; the label text is faint and disappears when the box is focused. A tool tip should give a little more description: "Type here to invoke a command such as menu item to invoke".

[[Image:OO_command_bar_proposal.png|600px|Command bar mock-up; please create a better one]]

== Use case ==

Jim uses Writer a lot, but inserts formulas rarely enough to forget how to do that. So every time he needs to insert a formula, he has to look through the menus. He guesses it may be under Tools, clicks on the Tools menu, but does not find anything related to formulas. Then
he opens the nearest candidate menu, Format, but again does not find anything. Next, he opens Insert, which sounds promising, but he still does not see anything about formulas. He closes the menu and visually scans the menu names again, then decides to look in Insert more
carefully. He consciously reads every menu in order until he reaches Object, which sounds promising. Finally, Jim finds Formula near the bottom of the Object menu, and selects it, feeling frustrated and stupid.

After installing OOo 3.0, Jim sees a new text input box labeled "Search" next to the traditional menu. He understands what it is for, thanks to the tool tip and his familiarity with URL bars. When he needs to add a formula inside Writer, he focuses the search box and
types "formula". Three items appear below the box, saying "View -> toolbars -> formula", "Insert -> Object -> Formula" and "Table -> Formula". Jim presses DownArrow, then Enter. Feeling satisfied and powerful, he enters his formula.

== Other uses ==
The same mechanism and the same box can be used for more uses:

# Searching Help without invoking the help window first. Thus the user's thought stays with the issue that needs help, rather than being interrupted by invoking the help app first, seeing the help interface and going to the right tab to search for the issue.
# Setting options. When you activate a command matching an option, the options window would open with the right tab and the option in focus. That would avoid searching through the huge maze of options.
# Inserting special characters: type "insert x" where x is the name of the character, such as "inf" for infinity.
# Opening files. When you start typing a file path, the result list shows names of directories that complete it. If type a directory path and a substring of a file name, the result list would show files in the directory, whose names contain the substring. Eventually, OOo may be able to rely on file indexes provided by the OS, such as Tracker and Beagle, so you don't have to type the file path, just the file name.
# Switching windows. If the query matches the name of a file that is already open, you can switch to the window showing the file.

== Placement ==

The consensus on the UX mailing list is to put the command (search) bar next to the menu bar, except perhaps for the MacOS version. There was discussion about putting it under the "Help" menu. It can also appear only when explicitly invoked, say under the Tools menu or by pressing F7; then it could replace the menu bar until it is dismissed by pressing Escape or a command is executed.

Putting the search box inside the Help menu would be more consistent with MacOS X's command search - see [http://picasaweb.google.com/photosofstuff/InsertTitleHere?authkey=lUpePSqMnis#5250481191941369218]. Consistency is important if everything else is equal, but here are some advantages to putting the command bar next to the menu bar.

# In plain view it is definitely more discoverable than under any menu.
# It is more inviting to use, so users are more likely to get the liberating benefits it provides.
# If it's under Help, users may think that it is only for getting help, while if it's next to the menu, that suggests it applies to other things.
# Even consciously knowing that there is a command feature under Help, in order to develop a habit of using it, users would have to break their association of the Help menu (including the window location and the shortcut Alt+h) with the thought of getting help.

Users probably will not look under Help before making effort on their own. This often avoids the detour through the Help system, which interrupts the user's task; it is a different mode of thought. By contrast, the command feature should be natural and seamless and the usual way to interact with the program.

Next to the menu bar it would look different than existing programs. But there is already a near precedent with the URL bar, which is perhaps more entrenched than MacOS's command bar in the Help menu. There are even tutorials on the Web about how to put their Firefox URL bar in the same row as their menu bar.

If the command bar is placed in the menu bar, it would be prominent, and so very accessible. It would also take up space that is free anyway. Resizing the window would resize the command bar, just like a URL bar in a web browser. If the window gets too small, the bar may eventually become hidden like other tool bars and even with the menu bar; or it could just break into a new line under the menu bar.

But in the end, a even command bar in the Help menu would be a great improvement over not having one at all.

== Other details ==

Command descriptions can be created by hand, with using menu item tool tip text, the text in the Help, and a thesaurus.

The synonyms can be extensible by for the user, and even easily shareable.

The history of executed commands should appear in reverse order if the user clicks on or presses the Down arrow key in an empty, focused query box.

The the result list should not obscure too much of the document. So, the size of the results box should be constrained (but not too small), and a scrollbar should appear if needed.

The result list can be ranked by relevance.

There may be an option to bring up the Help on what you're trying to do (like maybe have a divider and underneath the matching command, saying something like "View help for X command").

== Menu entries ==
[[User Experience/Command search/Commands]]

== Related projects ==
* All desktop command-search tools, such as Gnome Deskbar, Gnome Do, Apple Spotlight
* [http://rchi.raskincenter.org/index.php?title=Archy_in_the_Future Archy] and [http://www.humanized.com/enso Enso], libre partial implementations of Jef Raskin's book "The Humane Interface". Archy is a content-based system completely driven by commands which act on ordered selections as arguments. For example, to calculate 1+2, type "1+2", select it and execute the command Calculate. The result replaces the expression. Enso is a similar, though limited, tool for the desktop.
* [http://labs.mozilla.com/projects/ubiquity Mozilla Ubiquity], a command tool for the Firefox Web browser, where commands have arguments. No menu entries exist as commands so far.
* The [http://en.wikipedia.org/wiki/Acme_(text_editor) text editor Acme], plus all its clones. They do not search for commands - you have to know the right command name and arguments.

== To do ==
* Create a nicer mock-up with larger font
* Decide the exact text for the search box tool tip
* Create a mock-up of the unfocused search bar, showing the in-box label (grey) and a tool tip
* Compile a list of command names of menu items
* Add synonymous names
* File a feature request at [http://qa.openoffice.org QA.OpenOffice.org] so that developers can weigh in on implementation options (arguments, use of Ubiquity code)

[[Category:User_Experience|UI Ideas]]
[[Category:To-Do|User Experience\UI]]