manjaro-sway
wayland-protocols
manjaro-sway | wayland-protocols | |
---|---|---|
29 | 5 | |
675 | 141 | |
0.3% | - | |
9.3 | 4.8 | |
6 days ago | over 1 year ago | |
HTML | Meson | |
MIT License | GNU General Public License v3.0 or later |
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.
manjaro-sway
-
Should I continue to sway and wayland or return back to x11 i3?
I added a really short example for a keyboard configuration to our support document: https://github.com/manjaro-sway/manjaro-sway/blob/main/SUPPORT.md
-
Help with Manjaro Sway Edition
Your best bet is checking the Manjaro Sway GitHub at https://github.com/manjaro-sway/manjaro-sway You can search the Issues to see if anyone else is running into the same error or check the FAQ.
-
Which version of Linux Mint should I install on a semi garbage tier laptop for playing older games on?
If you want to see how nicely configured Sway looks like, then download the Manjaro Sway into your Ventoy2Disk formatted usb and try it by booting in Live mode: https://manjaro-sway.download/
-
[Manjaro Linux] Comment puis-je créer un USB amorçable de manjaro de manjaro?
[https://manjaro-sway.download/
-
Manjaro Sway users, we need your input!
Full discussion on GitHub- manjaro-sway/manjaro-sway/discussions/459
- Fullscreen on 2 monitors.
- Rofi .config gets overwritten
- I just installed yesterday what's going on?
-
i use manjaro, convince me to switch
Thanks for the honorable mention of Manjaro Sway edition! I always look a little towards nix, void an Solus too, but loosing the aur would be to big of a sacrifice for me.
-
So what are you guys using in stead of the Pi
Yep, though I tend to use Sway.
wayland-protocols
-
c-api for wayland input-method-unstable-v1
I was wondering which .so contains the symbols for https://github.com/wayland-project/wayland-protocols/blob/main/unstable/input-method/input-method-unstable-v1.xml.
-
Flameshot, powerful screenshot tool, fully support Wayland (able to run on sway)
I was researching the issue and noticed wlr-screencapture. I was hoping to see it at https://github.com/wayland-project/wayland-protocols too, but no luck. Thanks for the lead on xfg-desktop-portal.
It is fascinating watching the near decade-long journey as Wayland tackles screenshots.
-
Guide: Full Wayland Setup for Linux
> Nothing is thrown away -> xserver is there for exactly this reason. Adding the extension for a system with bad abstraction is not too wise, but if you wanted to understand it, you would have done so already based on the video.
I did watch the video, and while I was convinced that the X.org reference implementation was crusty, I was not convinced that there was anything inherently wrong with X11-the-protocol. Like, if there existed an X extension whose responsibility was just to get clients set up with their own video buffers that it could composite for them, then it sounds like it would address 90% of Wayland's value proposition. Is there a particular video snippet you want me to pay special attention to that clarifies this?
> Why would it be lost? There is a core protocol that absolutely specifies it.
I read through the stable interface definitions in the wayland-protocols repo [1], and did not see anything related to controlling which programs get to see which events. Is this still in development (or unstable)? If so, is there an ETA at which point I can expect every correct Wayland compositor to faithfully implement it?
> And when you had only one player in the whole game.. which is pretty contradictory to your last sentence.
That's because the X server implements the mechanisms, not policies, for multiplexing the screen and input devices. In the service of this, it provides tools to enumerate, identify, query, modify, and extend properties of windows, as well as route messages between them. There was never a compelling need for multiple competing incompatible X servers because X is the narrow waist (i.e. an unopinionated digital commons) shared by software that competed on policy.
> I didn’t address these things because basically everything has a solution under wayland nowadays. Please have a look at the wayland-protocol repo and see for yourself the state of it. Also, wayland is a display manager, just because the X server was a monolith, it had no place to eg. manage clipboard. Actually, Wayland is the one that fulfills the UNIX philosophy of do one thing (although I don’t find the UNIX philosophy a good thing in every case)
I read through the unstable interface definitions, and see that Wayland is indeed trying to implement not only the same kinds IPC facilities and input device multiplexing that X provided, but also is trying to impose stronger opinions on what types of windows exist and how they behave (e.g. Wayland has a notion of pop-ups, text inputs, and so on). So if Wayland's goal is to avoid being as "monolithic" as X, it appears to be failing.
Also, putting core functionality that everyone must implement the same way into extensions just so they can call Wayland "just a protocol" or "just a display manager" is disingenuous. They might as well just say that they're part of the core protocol.
> No, you just use wlroots that implemented the “crap-ton” of extensions for you already, and be on your way.
Does the wlroots project define what extensions are standard and required for a piece of software to call itself a Wayland compositor? No? Then "just use wlroots" isn't addressing the problem of making sure these compositors are compliant to a set of common, useful standards. Like, maybe wlroots should be the standard-definer, just as X was? What happens with window managers built with a compositor that is not wlroots?
[1] I was looking here: https://github.com/wayland-project/wayland-protocols
-
Plasma Wayland (session) Has Come a Long Way, But....
Virtual keyboard: https://bugs.kde.org/show_bug.cgi?id=427972 it is still a hot-topic on the protocol definition side with the current definition https://github.com/wayland-project/wayland-protocols/blob/master/unstable/text-input/text-input-unstable-v3.xml still not satisfactory, this was one of the subject of this weekend Plasma Wayland online Sprint. The Virtual keyboard is especially important for different input methods, aka chinese, japanese, koreans characters. You may want to setup http://maliit.github.io/ on your system.
-
[SimpleWM] Sometimes you just have to make things from scratch
The protocol XML files have remarkable, concise documentation of each request, event and interface. Core protocol. Other protocols.
What are some alternatives?
wayfire - A modular and extensible wayland compositor
peek - Simple animated GIF screen recorder with an easy to use interface
desktop-settings - forked desktop settings with sway profile
flameshot - Powerful yet simple to use screenshot software :desktop_computer: :camera_flash:
Waybar - Highly customizable Wayland bar for Sway and Wlroots based compositors. :v: :tada:
wtype - xdotool type for wayland
sddm - QML based X11 and Wayland display manager
labwc - A Wayland window-stacking compositor
grim - Grab images from a Wayland compositor
ly - display manager with console UI