KWin Effects that extend Wayland

[aleix.pol_gonzalez at mercedes-benz.com]

Dear KWiners,

Some recent developments in MBition required internally to have an effect that implements an internal Wayland protocol.


At the moment we expose KWaylandServer::Display *Effects::waylandDisplay() which is internal to kwin nowadays, so it makes it a bit harder to hook ourselves into it. Here's some not-too-much-out-there solutions I can think of:

- we connect to wayland separately from the effect.
- we expose wl_* pointers, then we figure it out on the effect side. In general, just wl_display should be fine, we might also need other pointers as the implementations need them, thinking of wl_output.
- we install kwaylandserver headers so it can be linked against.

What do you think would work best? IMO, the easiest would be installing the headers, this way we can reuse the work that already is there. We don't need to keep promises over this API.


Best,
Aleix with a new hat

If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kwin/attachments/20230613/527f0369/attachment.htm>