xdg-desktop-portal
wayland-explorer
xdg-desktop-portal | wayland-explorer | |
---|---|---|
154 | 25 | |
529 | 177 | |
2.3% | - | |
9.4 | 7.8 | |
4 days ago | 8 days ago | |
C | TypeScript | |
GNU Lesser General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
xdg-desktop-portal
- Flathub: One million active users and growing
- Changes to xdg.portals?
-
PCSX2 Disables Wayland Support
>Not losing all the work every time your windows manager crashes
https://news.ycombinator.com/item?id=37509703
>remapping keys
>Use xinput to change parameters of their input devices (libinput dropped most configuration options present with evdev)
Up to the compositor.
>Global shortcuts
Also up to the compositor. Was added to xdp in https://github.com/flatpak/xdg-desktop-portal/blob/main/data... so it's up to the compositor's xdp impl to provide it. It was created by a KDE dev so I assume KDE implements it at least.
>tunnelling over ssh
https://gitlab.freedesktop.org/mstoeckl/waypipe
-
Gnome developer proposes removing the X11 session
> - O proper screen recording support
Works just fine. I use OBS.
> - broken screen sharing
Never had any trouble with it.
> - No proper global keyboard shortcut
> - No push to talk support
On its way: https://github.com/flatpak/xdg-desktop-portal/pull/711 / https://flatpak.github.io/xdg-desktop-portal/#gdbus-org.free...
> - Several problems with multiple screens
Haven't had any more than on X11, but then again I do use Nvidia hardware on Linux.
-
The Guy Preserving the New History of PC Games, One Linux Port at a Time
It might help, but at this point Linux containers can't really stabilize the whole environment, especially for games. Particular pain points include accelerated graphics (which theoretically can have a stable kernel interface, but in practice is so complex and performance-sensitive that it's not stable enough to be a "reference platform", so to speak) and modern game controllers (which present a whole mess of concerns typically "addressed" in Flatpak by granting the device=all permission and hoping for the best [1]).
I also know a guy who ran into issues with a kernel update breaking a custom allocator, although I don't know the fine details. That wasn't for a game, but games also use custom allocators for various reasons.
[1] https://github.com/flatpak/xdg-desktop-portal/issues/536
-
Unpacking Elixir: Syntax
I don't use Wayland, but it seems xdg-desktop-portal since 1.16.0 has a 'Global Shortcuts portal'. Perhaps check it out.
https://github.com/flatpak/xdg-desktop-portal
-
UX Hurdles in Open Source #1: Flatpak Permissions
It's being discussed: https://github.com/flatpak/xdg-desktop-portal/issues/611
-
Advice: TW or Aeon
The first bug report was filed in early 2022 but unfortunately no progress yet on the matter, even after numerous similar reports ever since.
- Native messaging for Firefox
-
Xdg portal hyprland and launching gui apps
Yeah been having the same issue since I changed to using the unstable branch, supposedly noticed and fixed upstream for a few variants of the problem (different people with different configurations of DE and xdg-* deps installed report the same issue due to timeouts of the other portals)
wayland-explorer
-
PCSX2 Disables Wayland Support
Wayland is good until you hit the corner cases that they decided to abandon, without leaving any alternatives. We can always have extra protocol that can be optionally enabled, but good luck with standardizing that. It feels as if Wayland people are abusing their committee to keep Wayland as-is, instead of extending it. The protocol dashboard[1] doesn't look exactly good.
[1]: https://wayland.app/protocols/
-
Inter-process Communication between two programs on Linux.
Wayland is itself an IPC system (that uses UNIX domain sockets). I would make a custom Wayland protocol (if there isn't already an appropriate one available, look here: https://wayland.app/protocols/). You can define the protocol in XML and generate the boilerplate code in C using wayland-scanner. I assume smithay also has an equivalent of wayland-scanner.
-
The reality of Wayland input methods in 2022
https://wayland.app/protocols/ and https://wayland.freedesktop.org/docs/html/ are just API references.
-
Swingland: Recreating Java Swing for Wayland
Given I will be using most of the Wayland protocol to achieve anything (it's minimal) and Wayland is well specified then the 'start at the bottom and build up' design pattern fits. Wayland has a wire protocol based on a Unix socket, and usefully Java has supported Unix sockets since release 16, so I can write everything in Java to (de)serialise messages. This gets me going quickly, providing positive feedback that I'm on the right track..
-
Red Hat considers Xorg “deprecated” and will remove it in the next RHEL
The core is bare-bones, there are numerous standard protocols since, and many other are in standardization. Here is a site to review their state: https://wayland.app/protocols/
-
Unix philosophy and compositor development
There is some lock-in in some places where tools adopt a protocol that is only implemented by wlroots compositors, or only implemented by KDE, etc, but I suspect this will improve over time as protocols stabilise ( and you can browse the available protocols here: https://wayland.app/protocols/ )
- Wayland Explorer
-
X12
This link comes up in literally every Wayland thread and it is even more bullshit now than it was in 2013 when it was first posted (and it was bullshit then too). It is titled "the real story" but it is quite the opposite.
A few key points:
1) he laughs at how X has a bunch of extensions. https://wayland.app/protocols/ hypocrites much. In 2013, since it was completely unusable, it probably didn't have many. But turns out real world use leads to "useless" features being reimplemented.
2) he complains about how X.org has broad hardware compatibility. As if that's a bad thing. Meanwhile wayland, even now it still doesn't work reliably on half the graphics chips on the market.
3) It complains that certain X features are not fully network transparent. True, but most are and you can detect at runtime and gracefully degrade. Wayland "fixes" this by just dropping the whole feature.
4) it flat-out lies saying the X server does nothing yet it is so much hard to maintain code. The core X protocol provides backward compatibility and is rock solid (and really easy to impelment from scratch btw, someone did it in Javascript for a tutorial for crying out loud). Meanwhile the Wayland compositor keeps accumulating everything because of point 1. Need a screenshot? Add it it the compositor. Need a hotkey? Add it to the compositor. Need drag and drop? Add it to the compositor. Need a notification icon? Add it to the compositor. In X, all those are peer to peer. Graphics are actually a relatively small part of a graphical user interface, something Wayland is still slow to learn.
5) He complains that certain applications are written inefficiently with blocking calls which is inefficient over a network connection. Wayland's calls are ALL blocking and just has no network connection.
6) Complains that X may draw things unnecessarily. Indeed... but there's an extension to disable that. Easy fix. Wayland even uses the same drivers!
- A better way to read Wayland documentation
-
Is it placebo or is X11 more stable than Wayland
So that brings me to Wayland Protocols!. In X11 land, X11 defines a lot of behaviors for you. There is no such definition in Wayland-land by design - this is to give compositors a lot more freedom and flexibility in how they function. It also means that it required time for protocols to develop to cover all of the things that we would need in a desktop window compositor to bring it up to snuff for desktop usage. These protocols evolved through the past 4-5 years of everybody seeing it's shortcomings on a Desktop system compared to a mobile phone based UI. With the latest fractional scaling protocol we have more or less finally "closed the gap" between Wayland and Xorg on the desktop - it's just a matter of compositors implementing full support for all of the protocols people want.
What are some alternatives?
gamescope - SteamOS session compositing window manager [Moved to: https://github.com/ValveSoftware/gamescope]
Pion WebRTC - Pure Go implementation of the WebRTC API
wayfire - A modular and extensible wayland compositor
kondo - Cleans dependencies and build artifacts from your projects.
gtk-layer-shell - A library to create panels and other desktop components for Wayland using the Layer Shell protocol
tera - A template engine for Rust based on Jinja2/Django
pipewire - Mirror of the PipeWire repository (see https://gitlab.freedesktop.org/pipewire/pipewire/)
gnome-gesture-improvements - Touchpad gesture improvements for GNOME on Wayland/X11
flatpaks
Zip Foundation - Effortless ZIP Handling in Swift
us.zoom.Zoom
rupy - HTTP App. Server and JSON DB - Shared Parallel (Atomic) & Distributed