HardyDesktopEffects

Revision 1 as of 2007-10-31 13:46:32

Clear message

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.

  • Launchpad Entry: hardy-desktop-effects

  • Packages affected: compiz, compiz-core, compiz-plugins, compiz-fusion-plugins-main, compiz-fusion-plugins-extra

Summary

  • Top compiz bugs
  • Xorg/driver related bugs
  • Compiz 0.7
  • Middle-ground between desktop-effects and ccsm
  • Default effects changes from feedback
  • New plugins/opportunities
  • Expose compiz keyboard shortcuts in UI
  • Less insane compiz shortcuts
  • Review compiz use of shortcuts to make consistent
  • Compiz shortcuts should work after purging metacity

Release Note

Run compiz as the default compositing/window-manager on supported graphics-hardware.

Rationale

Running compiz (as default instead of metacity) is meant to be as smooth and non-intrusive as possible, while improving the visual appeal and accessability of the default desktop-setup. The user should only recognize the improved visual appeal and added usability-improvements on the desktop. There should be as little breakage as possible moving from metacity to compiz in terms of behaviour, keyboard-shortcuts and themes.

Use Cases

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

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.

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

  • redirected direct rendering (OpenGL-apps not working properly unter compiz, if run on system using DRI-based drivers... that means all OpenSource-drivers at the moment)

BoF agenda and discussion

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.


CategorySpec