HardyDesktopEffects

Revision 4 as of 2007-11-01 16:47:39

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
    • - Listen to changes for RandR configuration. New displays/new sizes/rotations.
  • Xorg/driver related bugs
  • Compiz 0.7
    • - Not sure if we can rely on 0.7 as of now. However 0.6 will likely not be actively maintained
      • will have to contact David, to find out. This is not overly important to decide on now.
      - Large parts of core are being rewritten. Using object system. - XRender output, ability to run without OpenGL, but requires accelerated 2d video
      • -> should be as fast/slow as metacity

      - we need to check if 0.7 is better than 0.6 basicly, as there is currently
      • not a lot of new stuff (it seems to be at least)
  • Middle-ground between desktop-effects and ccsm
    • - simple-ccsm with UI tweaks - port appearance capplet to use libcompizconfig so that profiles
      • can be used there to save custom settings
  • Default effects changes from feedback
    • - scaleaddons - scalefilter (+ enable case-insensitive) - add live-preview on extra effects for wall (in the change animation)
  • New plugins/opportunities
    • - session-management plugin
  • Expose compiz keyboard shortcuts in UI (gnome-keyboard-shortcuts?)
  • Less insane compiz shortcuts
    • - remove everything and put back only important ones - add them to the gnome-keybinding propoerties capplet (compiz-keys.xml) - Standardize on use of super key as a binding. - Allow super key to be changed out for another key.
  • Review compiz use of shortcuts to make consistent
    • - Super key.
  • Compiz shortcuts should work after purging metacity
  • make compiz features more discoverable:
    • - hotcorners with a modifier (?) - window manager menu with additional compiz features - have a menu on the workspace switcher that exposes
      • functionality (scale, expose) + the keybindings
      - Display shortcuts where users are likely to look for them. i.e. when right
      • clicking on pager shows keybindings for move viewport, expo, so on, so forth.
  • fix the problem that when metacity is purged the keybindings break
    • (integration mode should write both compiz and metacity settings)
  • Decorator
    • - New one, written in C. - Need SVG backend. - Dennis mentioned:
      • A window decorator could be written that unredirects the window, makes a frame window, and reparents the window to it's decoration. After this all painting code in compiz is disabled, and then you have a 2D version of Compiz that will work without Compiz/OpenGL (we would still need a new 2d switcher plugin).
  • we have issues with multihead
  • session-management: YES! (talk to amaranth and try to get it upstream)

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)

  • the current migration of workspace-layout from metacity to compiz is a unpleasant workaround, because the number of rows of the workspaces under metacity is a property of the wnck-applet and not metacity... after speaking with upstream the [http://standards.freedesktop.org/wm-spec/wm-spec-latest.html EWMH-spec] needs to be extended to make this cleaner in the future

BoF agenda and discussion

Sander Smid: Perhaps add AWN as the launcher / taskbar replacement since they now support applets. More info at http://wiki.awn-project.org/index.php?title=Main_Page (demo at: http://awn.wetpaint.com/page/Demo)

Mirco Müller: AWN will not be a default panel- or taskbar-replacement for Hardy. But it would be reasonable to have it available in universe, thus people who want it can install it easily. Maybe if interested developers push hard for it (to make it a solid alternative to the gnome-panel) it could be considered for Hardy+1.


CategorySpec