swayfx VS sway

What are the chances of SwayFX being added to the repo ? I see someone had put in a PR but it was never accepted and also the package is now at version 0.3 whereas the person who put in the PR is still at 0.2 since April. Would it be bad practice for me to put in an updated PR that works as I'd be keen to maintain that package for sure ?

I forked sway and added em myself! https://github.com/WillPower3309/swayfx

yes, it is possible with SwayFX

Switch to Arch Linux with Wayland & https://github.com/WillPower3309/swayfx. Then add https://github.com/Alexays/Waybar for status bar.

If sway is your Wayland desktop, check out swayfx.

WM: swayfx

Most commonly, the scratchpad is used as a "minimize." There is an open issue to treat it as an actual minimize in terms of wlroots, which it currently does not do and, the issue states, can cause a crash when trying to un-minimize applications that are currently hidden on the scratchpad. You can see the github issue for more info here. There is also a patch available (link in the issue discussion) that adds the minimize functionality if you're willing to compile it yourself. I have not tested it since I don't use a taskbar and just throw unused windows into another workspace until I need them. SwayFX, a fork that was just released, which I'm currently running for the window decorations has this patch already applied.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).

Sensitive features like screenshots, input methods, screen locking and whatnot are behind extensions (or portals). I'm not familiar with the state of GNOME/KDE/Flatpak, but at least on the wlroots side of things it is true that currently these extensions are enabled and accessible by any process that can talk to the Wayland socket (breaking those security benefits, as you say). This is changing with protocols such as security-context that allow a sandbox engine like Flatpak (or your custom scripts) to restrict what features apps can use. (so your browser can't register an input method, or some random app can't lock the screen)

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...

https://github.com/swaywm/sway/pull/7648

https://github.com/flatpak/flatpak/pull/4920

sway does all those things very well: https://swaywm.org/

I've added it to https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

https://github.com/swaywm/sway/issues/4763

sad to see another linux api design failure

Read the manual on https://swaywm.org/. There are tons of youtube videos showcasing basic configuration and usage. This is extremely basic stuff you need to do yourself.