HardyDesktopEffectsShortcuts

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2007-12-17 11:00:55 →
Size: 4596
Editor: dslb-084-063-123-148
Comment:
← Revision 4 as of 2007-12-17 11:40:24 → ⇥
Size: 3946
Editor: dslb-084-063-123-148
Comment:
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
See also:
 * [https://wiki.ubuntu.com/DesktopTeam/Specs/HardyDesktopEffects hardy-desktop-effects]
Line 17: Line 14:
When using compiz enabled via the "Visual Effects"-tab users can expect every major keyboard-shortcut they know from metacity to trigger the same funtion under compiz. Additional features of compiz not available in metacity are exposed as shortcut-hints in menus or tooltips where appropriate. When using compiz/"Visual Effects" users can expect every major keyboard-shortcut they know from metacity to trigger the same funtion under compiz. Additional features of compiz not available in metacity are exposed as shortcut-hints in menus or tooltips where appropriate.
Line 61: Line 58:
gnome-keyboard-properties has to expose all default keyboard-shortcuts used by compiz. A XML-file is used for populating the list of keyboard-shortcuts in gnome-keyboard-properties.

Shortcut-hints have to be added in a window-menu rendered by the decoration plugin.

Shortcut-hints have to added as tooltips in workspace-switcher applet.
Line 69: Line 61:
Should cover changes required to the UI, or specific UI that is required to implement this gnome-keyboard-properties has to expose all default keyboard-shortcuts used by compiz. A XML-file is used for populating the list of keyboard-shortcuts in gnome-keyboard-properties.
Line 71: Line 63:
=== Code Changes === Shortcut-hints (metacity-functionality) have to be added in a window-menu rendered by the decoration plugin.
Line 73: Line 65:
Code changes should include an overview of what needs to change, and in some cases even the specific details. Shortcut-hints (compiz-functionality) have to be added as tooltips in workspace-switcher applet.
Line 77: Line 69:
Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.		 The compiz-shortcuts need to be protected from a possible purge of metacity-shortcuts in gconf.
Line 90: Line 79:
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.  * [https://wiki.ubuntu.com/DesktopTeam/Specs/HardyDesktopEffects hardy-desktop-effects]
Line 92: Line 81:
== BoF agenda and discussion == == Discussion ==
Line 94: Line 83:
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

Improving the integration of compiz into the GNOME-desktop needs trimming down the keyboard-shortcuts to sane defaults, making them map 1:1 to metacity's default keyboard-shortcuts and make keyboard-shortcuts for additional compiz-functionality easily discoverable without the user being required to skim the web for documentation about these additional keyboard-shortcuts.

Release Note

When using compiz/"Visual Effects" users can expect every major keyboard-shortcut they know from metacity to trigger the same funtion under compiz. Additional features of compiz not available in metacity are exposed as shortcut-hints in menus or tooltips where appropriate.

Rationale

Switching a central part like the window-manager should not force the user to relearn common keyboard-shortcuts.

Use Cases

  • Kim used to run Ubuntu 6.06 LTS and recently upgraded to Ubuntu 8.04 LTS. Her machine is capable of running "Visual Effects", which are enabled by default upon first login after the upgrade. Although compiz is running now as her default window-manager she expects the keyboard-shortcuts to work as before. The only change she should recognize is that everything now elegantly animates and looks slicker.

Assumptions

The default "compiz modifier" will be the Super-key. This is meant to be the modifier for triggering functions specific to compiz (e.g. expo, scale). That is meant to avoid mapping conflicts with shortcuts used in applications. The use of shortcuts used by compiz needs to be consistent across all compiz core-features and plugins.

Design

Default keyboard-shortcuts that need to be taken care of (metacity-functionality):

  • switch to next workspace
  • switch to prev workspace
  • switch to 1st, 2nd, 3rd... workspace
  • trigger move window
  • trigger resize window
  • trigger close window
  • switch to next window (on current viewport)
  • switch to previous window (on current viewport)
  • switch to next window (on all viewport)
  • switch to previous window (on all viewport)
  • minimize current window
  • maximize current window
  • shade current window
  • move window to next workspace
  • move window to previous workspace
  • move window as is (Alt-LMB drag)
  • resize window as is (Alt-MMB drag)

Default keyboard-shortcuts that need to be taken care of (additional compiz-functionality):

  • trigger/exit expo
  • trigger/exit zoom
  • trigger/exit scale

Implementation

UI Changes

gnome-keyboard-properties has to expose all default keyboard-shortcuts used by compiz. A XML-file is used for populating the list of keyboard-shortcuts in gnome-keyboard-properties.

Shortcut-hints (metacity-functionality) have to be added in a window-menu rendered by the decoration plugin.

Shortcut-hints (compiz-functionality) have to be added as tooltips in workspace-switcher applet.

Migration

The compiz-shortcuts need to be protected from a possible purge of metacity-shortcuts in gconf.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.

Outstanding Issues

Discussion

CategorySpec

DesktopTeam/Specs/HardyDesktopEffectsShortcuts (last edited 2008-08-06 16:14:28 by localhost)