wlr-protocols

No Wayland support[1] still. Interestingly there are "donations" being accepted & some kind of a bounty for this issue. I don't know if anyone can deem the bounty, but it looks like it might be for $2500! Wow. When this issue was opened almost 3 years ago, I think support would have been much harder, but there are wayland protocols like wlroots's wlr-virtual-pointer-unstable-v1[2] now to regularize/normalize this sort of thing. In general, there are just so so so many open issues & pull requests open. It's great software but wow, there's so many different environment's it needs to work across, & trying to maintain this project seems like a nightmare. Not cross platform afaik but I really dig the netevent[2] project linked in this thread, which is a lower-level network input forwarder. Last but not least, Barrier was discussed on HN with 1

For your reference, these are the issues to subscribe to if you're interested in following the discussion as it's taking place: https://github.com/emersion/xdg-desktop-portal-wlr/issues/12 https://github.com/swaywm/wlr-protocols/issues/93

It's not a particularly arduous "adventure". We maintain a list[0] of programs which use these protocols. And wlroots != tiling window manager: there are multiple wlroots-based compositors which do not use the tiling paradigm, the most developed of which is probably Wayfire[1]. [0]: https://github.com/swaywm/wlr-protocols/wiki [1]: https://github.com/WayfireWM/wayfire

Why don't you propose a protocol to solve the issues you have? If it solves a problem other users have it would get adopted I'm sure (except maybe GNOME). I'm not a Wayland developer but it's what I observed in the issue tracker of my WM. A limitation is often overcome by a protocol and a basic implementation after. If you put the work in, the wlroots and KDE people are always very nice and will help you get started. https://github.com/wayland-project/wayland-protocols/tree/ma... https://github.com/wayland-project/wayland-protocols/tree/ma... https://github.com/swaywm/wlr-protocols/tree/master/unstable

The wlroots developers have proposed protocols for screen grabbing etc. which are already supported by some window managers (e.g. Sway) and by some applications. https://github.com/swaywm/wlr-protocols

The wlroots developers are working on protocol extensions to make stuff like screen grabbing work consistently across WMs: https://github.com/swaywm/wlr-protocols

We have designed a new Wayland protocol for this kind of apps: https://github.com/swaywm/wlr-protocols/blob/master/unstable... So yes, it's possible. I'm not aware of any existing drop-down terminal using the protocol yet.

No, it won't work. There are some possible replacements (e.g. [1]) but it's still a work-in-progress. [1]: https://github.com/swaywm/wlr-protocols

>It's not bloated X11 has a big number of issues. Security, very complicated mechanisms (like how clipboard is handled), HiDPI are some of these issues. X11 _is_ bloated (for instance it has an drawing API). It's not like Wayland makes things that were possible on X11 impossible, it's just that replacements for everything don't exist yet. For instance there's no standardized way to make panels/docks/notification daemons. Same goes for screenshooters and screen recording. We -- the wlroots developers -- have been campaigning to push new protocols to bridge the gap. For instance the layer shell mentioned in the article is a protocol we try to standardize [1]. [1]: https://github.com/swaywm/wlr-protocols/blob/master/unstable...

This is FUD. One of wlroots core goals from day one has been to promote the standardization of cross-desktop protocols that allow for these features. We have already addressed two of the points you brought up, namely screenshots and screen casting, via these protocols: https://github.com/swaywm/wlr-protocols/blob/master/unstable... https://github.com/swaywm/wlr-protocols/blob/master/unstable... There are several more protocols we have written and are working on to address similar concerns: https://github.com/swaywm/wlr-protocols/issues 3 delegates from wlroots, including myself, who together represent 8 distinct Wayland compositors, are joining 3 delegates from KDE at XDC 2018 to discuss the standardization of these protocols and propose them for integration across the whole ecosystem.

We haven't forgotten about you, but we could use your help if you want it done fast. We've made some important progress towards supporting this functionality recently. A protocol our people have been working on is currently undergoing standardization[0] which enables software keyboard devices. A similar protocol could enable software pointer devices. We also made another[1] protocol for efficiently capturing the contents of the display. Plug all of these together and an RDP server is probably possible. Maybe a few weeks of work with FreeRDP for the motivated programmer. My email is in my profile, reach out if you want to make some connections and get started. [0] https://lists.freedesktop.org/archives/wayland-devel/2018-Au... [1] https://github.com/swaywm/wlr-protocols/blob/master/unstable...

>I guess the question really is, could you write a general compositor, which just handle inputs and output, and then use that compositor to run any number of different desktop environments where the authors technically doesn't need to worry about Wayland? This is a goal we're working towards in the wlroots camp. You could do this, but the issue would be running a lot of the things that tend to define the desktop environment, such as the panel, menus, desktop feel, etc. In order to support that, we need a Wayland protocol that lets clients have some say in where they are displayed on-screen, such as a taskbar wanting to be shown across the bottom. For wlroots we made such a protocol[0], and it is slowly being adopted across the ecosystem. Porting DEs to use it would be a great way to help improve Wayland :) [0] https://github.com/swaywm/wl

That's not quite true: the compositor needs to support it. There's a protocol [1] for it that's supported by a redshift with a patch [2]. It also works out the box for any wlroots-based [3] compositors, like sway [4]. [1] https://github.com/swaywm/wlr-protocols/blob/master/unstable... [2] https://github.com/minus7/redshift/tree/wayland [3] https://github.com/swaywm/wlroots [4] https://github.com/swaywm/sway