Binding to all key events in libweston-desktop
Is it possible to have a callback function for *all* key events using weston_compositor_add_key_binding () in libweston-desktop? Are the modifiers passed to the callback function, or only the keycode? Regards adlo
Re: Protocol for window previews/thumbnails
Thanks for your feedback too. On Wed, May 11, 2016 at 2:51 PM, Derek Foremanwrote: > > > But I'm of the opinion that this doesn't need to be a "wayland" problem > at all - but I'm not saying there can't be a standard way to do this. > > It just doesn't need to be solved by adding wayland protocol. A common > module framework for compositors that find this functionality useful > would probably perform better and have less complexity. > Do you mean something like a shared library that compositors can link against? Does this mean that compositors would not have to have their own implementation of this functionality as it would be provided by this library, or have I understood this incorrectly? Regards adlo ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Protocol for window previews/thumbnails
Thank you for the feedback, that was very helpful. On Wed, May 11, 2016 at 9:07 AM, Pekka Paalanenwrote: > > > You should explain the use case behind the idea. Then it would be > possible to assess whether such protocol would even be appropriate for > it. > My use case is third-party window switcher applications, such as xfdashboard or my program, xfce4-lightdash-plugin: https://github.com/adlocode/xfce4-lightdash-plugin If some sort of protocol would be needed, then you have to figure out > how to not make it a gaping security breach > Perhaps the security could be improved by having a permissions system where only authorised programs are allowed to use this protocol? Maybe the compositor could expose a settings framework that allows the user to control the permissions of applications. A little more tractable plan would be to communicate only surface > meta-data to the client, which could then ask the compositor to draw > the thumbnails relative to one of the client's surfaces. The client > would never have access to window content itself. That's a good point; this could be a good solution, as long as it is toolkit-independent and supports all rendering methods: OpenGL, pixman 2D software rendering, etc. However, then there's the question of whether it can be a standard protocol or not. It is important that it is a standard, cross-compositor protocol. For example, if I am using my app on "xfwm-wayland" and then I decide that I want to switch to KWin, my app should continue to work. Regards adlo ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Protocol for window previews/thumbnails
I think that it would be a good idea to have a standard, cross-compositor protocol for getting previews/thumbnails of windows, similar to XComposite. This protocol should be as fast as possible and use as little system resources as possible. It should probably provide a handle to the native window surface. It will also be necessary to receive damage events on these surfaces. I don't know if this should be included in this protocol or if this should be a separate protocol? Does anyone have any ideas on the best way to design such a protocol? Thank you Regards adlo ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel