For the global keyboard shortcut problem, what about making it similar to the others like virtual keyboards and have weston only trust an application that it launches? Then there could be several possible applications: one which has no security and lets any program access the keyboard similar to how X works. As an alternative, desktop environments could provide a different program which listens for global keypresses but instead of handing out the raw keypresses, use dbus + policykit to pass events like volume up, volume down, etc to any application that policykit authorizes.
This has the advantage of using already existing authentication infrastructure (policykit) and not force weston to define an explicit list of events.
Posted Sep 26, 2012 13:52 UTC (Wed) by mupuf (guest, #86890)
[Link]
This solution seems a bit over-complicated to me. The solution presented in the article can leverage policy kit too and doesn't necessitate another daemon neither dbus.
However, a lot of work is left to be done on all this matter. We don't pretend to understand every valid use cases and the need of every applications so I may not be able to understand your point.