On 11/22/2010 12:21 PM, Henrik Rydberg wrote: > If the question is whether we want to enable gestures spanning more than one > application/window, it seems the answer is yes. Given that, using a global > gesture recognizer is efficient. Putting it in the window manager then makes a > lot of sense. > > To further elaborate on possibilities, it might be fruitful to consider what > the > differences are to the current (maverick) architecture. For instance, if there > was a gesture protocol through X, we could implement the sought features > without > the wm. If there was no X, we could implement the sought features solely in > the > wm. If there was no wm, we could implement support directly in the > application. > In my view, there are many possibilities, but the one presented by the team > keeps a balance between where we are (X and no gesture protocol), what we want > (wm with global gesture support) and where we are going (wayland etc).
I've been involved in this discussion on IRC as well, so I just wanted to say that from a high level I concur with what Henrik wrote above. Beyond what Henrik wrote, I think there are ways to optimize the architecture if a gesture is recognized as application specific. However, the method I came up with was convoluted and tricky, so I think we should continue with the architecture as it is and see if the extra WM wakeups really are an issue. If they are we can take another look at the convoluted tricky architecture (or just speed up wayland development :). Thanks, -- Chase _______________________________________________ Mailing list: https://launchpad.net/~multi-touch-dev Post to : multi-touch-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~multi-touch-dev More help : https://help.launchpad.net/ListHelp
