The dependency of Unity on certain Compiz plugins must die!
It appalls me that the Unity developers seem to take pride in making sure that editing the Compiz plugin setup will crash Compiz. Bug 685552 wasn't fixed by the tying of Unity to specific Compiz plugins, it was made worse! Who wouldn't want the Cube, Cylinder, or Sphere effects in Unity? What about the Magic Lamp effect? The Shift Switcher? How about the ability to change the opacity of windows? The whole reason why the controversy started over GNOME Shell was because users could no longer use the Compiz Cube, Magic Lamp, Shift Switcher, and other neat effects. Now Unity claims to fix that problem by using Compiz, but then locks you into a set of plugins that does not include any of these features.
Blueprint information
- Status:
- Not started
- Approver:
- Mark Shuttleworth
- Priority:
- Undefined
- Drafter:
- Mark Shuttleworth
- Direction:
- Needs approval
- Assignee:
- Mark Shuttleworth
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
The whole reason why Unity crashes when plugins are enabled or disabled is for two reasons: (1) the fact that Unity depends on a specific plugin set, and (2), as Sam Spilsbury pointed out, the fact that the Unity plugin doesn't stop and start again when plugins are enabled or disabled in CCSM, causing sigc to freak out. Get rid of both these simple problems, and this blueprint will have been lived up to.
