Difference between revisions of "Mac OS X Porting - Keyboard Shortcuts"

Revision as of 18:32, 24 February 2007

Contributors

• Ismael Merzaq: Ismael
• Mox Soini: Mox

Introduction

For most of the keyboard shortcuts in OpenOffice.org, the Mac OS X port will follow the other OpenOffice.org platforts, to maintain consistency and allow people to use several platforms without much re-learning.

However, there are some special cases that require Mac OS X port to make exceptions in shortcuts, compared to the other platforms:

• Mac OS X System has global keyboard shortcuts that override existing OpenOffice.org shortcuts
• Apple Human Interface Guidelines (AHIG) requires that all Mac OS X applications define certain common set of shortcuts. That common set might cause a change for shortcut to have different functionality.

  Example:
  Some key accelerators are already used by Mac OS X, and so Mac OS X catches them and does the associated action,
  causing OpenOffice.org to not see them. 
  
  For example, when we press F9 in openoffice (native version or X11 version), the fields aren't refreshed, 
  because the Mac OS X function Exposé is launched and catches the key accelerator (to refresh the fields, go to
  tools>refresh>fields in the menu.
  
  What we have to do is to change the conflicting key accelerators for OpenOffice.org.

Mac OS X Shortcuts

• OOWriter:
  • cmd+space ==> shows spotlight instead of adding a non breaking space
  • F11 ==> shows the desktop instead of showing the style dialog
  • F9 ==> shows exposé instead of refreshing fields
  • shift+cmd+space ==> is Apple reserved, in OOo is used for default format in format menu (see http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGKeyboardShortcuts/chapter_20_section_1.htmlbreaking)

• OOCalc:
  • F9 ==> shows exposé instead of recalculing the cell content (tools>cell content>recalc)
  • F12 ==> shows dashboard instead of doing Data>Plan>Group

Following Apple Human Interface Guidelines in menus

The second problem which is not really a problem is that we have to change some key accelerators if we want to respect the Apple Human Interface Guidelines (AHIG) (Apple Human Interface Guidelines and mostly AHIG for key accelerators and menus and for menu exemples ) Here's a list of key accelerators which doesn't correspond to Apple Human Interface Guidelines:

• The key accelerator used in OOo refers to another function in AHIG:
  • cmd '-' (hyphen):
    • in OOo: adds a "conditional hyphen" ("tiret conditionnel" in french)
    • AHIG: Decrease the size of the selected item (equivalent to the Smaller command).

• The function uses in OOo a key accelerator which is different than the one specified in AHIG
  • SpellCheck:
    • in OOo: F7
    • AHIG: cmd+';' (semicolon) and should be in the edit menu
  • Preference window:
    • in OOo: in the menu Tools>options without key accelerator
    • AHIG: key accelerator cmd+',' (comma), and located in “The Application Menu”
  • Opening Help:
    • in OOo: F1
    • AHIG: cmd+? (question mark)
  • Redo command:
    • in OOo: cmd+Y
    • AHIG: shift+cmd+Z
  • non breaking space
    • in OOo: cmd+space
    • for macos: Option+space (see http://en.wikipedia.org/wiki/Non-breaking_space)
  • Close window
    • in OOo: in the window menu with the key accelerator and the text "close the window" and in the file menu without key accelerator and with the text "close"
    • AHIG: in the file menu with the text "close" and with the key accelerator cmd+W
• The function hasn't a key accelerator in OOo but should have one to follow AHIG
  • Save as
    • shift+cmd+S
  • Left-align a selection
    • cmd+{ (left bracket)
  • Right-align a selection
    • cmd+} (right bracket)
  • Center-align a selection
    • cmd+| (pipe)