http://bugs.opencompositing.org/show_bug.cgi?id=976
Danny Baumann <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
--- Comment #1 from Danny Baumann <[EMAIL PROTECTED]> 2008-06-20 12:19:49 ---
(In reply to comment #0)
> == Affected Plugins ==
>
> - application switcher
> - ring switcher
> - shift switcher
> - stack window switcher
> - static application switcher
> - are there any more
>
>
>
> == The Problem ==
>
> Each of the aforementioned plugins implements the same functionality. The only
> difference between these plugins is the animation / visual appearance.
>
>
>
> == Consequences ==
>
> Each of these plugins has its own key bindings. Enable two of them
> simultaneously and you get "conflicts" because of identical bindings. To avoid
> these conflicts some of these plugins use individual keybindings, so the user
> has to configure or learn those.
> Also it is inconvenient for the user to activate deaktivate multiple plugins
> to
> change the effect / visual appearance of the application switcher.
I thought about that as well, but there are a few issues with that:
> == Possible Solution / Suggestion ==
>
> Look at the "animation" plugin -- One plugin cares about all the logic, key
> bindings, events, whatsoever ; an then triggers the fitting animation.
> Do the same for application switcher. One plugin cares about keybindings, the
> internal logic of switching between applications (i.e. the list of windows)
> etc.
> And then just trigger a child-plugin, that just implements the visual
> apperance.
It might make sense to enable two switchers (e.g. one for fast switching, one
for good overview - imagine staticswitcher vs. ring).
> == Benefits ==
> - No more conflicts: Only one plugin means no conflicting plugins
Right.
> - Improved usability: Less Plugins in ccsm gives the user a better overview.
> - Simplicity: Switching the visual apperance is as easy as a dropdown
> selection
No. One subplugin per effect would mean as many plugins as we have now.
> - No more redundance: All the Key bindings are in one place
Right.
> - Efficiency: Only one plugin to maintain.
No. We'd still have one main plugin + n child plugins.
> I am sure this concept could be applied to any other sort of plugins and not
> just application switchers. But these are the ones that are most annoying to
> me.
What other examples do you have in mind? ;)
--
Configure bugmail: http://bugs.opencompositing.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Dev mailing list
[email protected]
http://lists.compiz-fusion.org/mailman/listinfo/dev
