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

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):

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

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

why not map all the effects to the windows key. It makes remembering the combinations easy... seing that we're mostly dealing with manipulating windows. Most keyboards come with this key. For ones that don't, an alternate combination can be used [ctrl+alt]. The point is to keep this base key(s) consistent for compiz. Here is the mappings I care about ([W*] = windows key) and that I'm currently using:


CategorySpec

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