[PATCH wayland-protocols] unstable: add xcursor-configuration
Drew DeVault
sir at cmpwn.com
Mon Dec 10 17:09:33 UTC 2018
On 2018-12-10 3:24 PM, Jonas Ã…dahl wrote:
> This reason comes up everytime D-Bus is mentioned, and I think it's
> somewhat counter productive; I don't think this is a problem clients
> should try to avoid so hard. D-Bus is more or less the universal IPC on
> Linux, is used quite extensively to allow sandboxed client to
> communicate with the outside world, and is almost guaranteed to be
> available everywhere.
Nothing about Wayland limits us to Linux. We try to think more broadly,
wlroots supports FreeBSD for example.
Even without that, it's just about making the right design decisions.
The Wayland protocol is used to communicate about the cursor, and it
will be rendered by the compositor. The client and compositor already
speak Wayland to each other. To me, the ownership over this information
clearly lies in this relationship and using side-channels to communicate
this information is a bad design.
More information about the wayland-devel
mailing list