- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
The ext-image-capture-source-v1 and ext-image-copy-capture-v1 screen copy protocols build upon wlroots’ wlr-screencopy-unstable-v1 with various improvements for better screen capture support under Wayland. These new protocols should allow for better performance and window capturing support for use-cases around RDP/VNC remote desktop, screen sharing, and more.
Merge Request: Create ext-image-capture-source-v1 and ext-image-copy-capture-v1
under the definition of bike shedding in the Encyclopedia you’ll find wayland the prime example. been waiting years on one pr for them to decide on the word “may” vs “will”
It drives me crazy. Just release it 18+months ago and iterate with versions, at least your users will have the feature in their hands.
That’s how you get the Zoom problem, where a Zoom developer decided to be nice and port their program to Wayland before screen capture was implemented well, resulting in a “workaround” that took screenshots in a loop rather than move to the proper API.
The API has been in the hands of people and developers for months, just not those who like their system to be moderately stable.
It is kind of shooting at the ambulance, zoom needs to also adapt to the new API. The alternative is a completely non functional Wayland for videoconferencing for years… Unusable stable is not better than unstable usable IMHO at least you have a shot at fixing it for the second option.
Yes, of course. But jumping on early with an incomplete API isn’t just something Zoom does. Plenty of applications are broken because they don’t receive complete API rewrites every few years.
Plus, it’s not like desktop Linux didn’t already ship a screen casting API. If developers wanted an unfinished/unstable API, they could’ve just implemented Gnome’s DBUS based API, that’s been around for years. No need to use something wlroots specific. Plus, the Gnome API also works on X11.
I assume they went with way land as a compromise.