this post was submitted on 22 Jun 2024
19 points (100.0% liked)
Linux
5373 readers
46 users here now
A community for everything relating to the linux operating system
Also check out !linux_memes@programming.dev
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Automatable (configuration-less) is indispensable. I got used to it with bspwm, and after using that for a while, switched to herbstluftwm and realized I'm stuck. I don't think I can go back to a WM with a configuration file anymore. Even the different between i3 and fully config-less like hlwm is stark once you're on the other side.
What does this mean? You do a manual action once and it always uses that position?
It means that anything you can do, set, or configure in the WM, you can do through a CLI RPC mechanism. There is no configuration file, no custom config syntax. The "config" is just a shell script full of these commands that herbstluftwm calls when it starts. Literally any behavior you can configure or make happen, you can do with these command line calls.
Alright, well, I haven't looked into the Wayland tiling window managers yet, so I can't say, if there's maybe something that fits exactly right, but anyways.
You should be able to customize the rule to fix that. In the property "Window types", deselect "Dialog Window" (or frankly probably everything except "Normal Window").
As for a more lightweight option, you could keep an eye out for LXQt. They don't have Wayland support ready yet, but plan a release this autumn: https://lxqt-project.org/blog/2024/04/15/wayland_faq/
It integrates various things from KDE and the KDE apps should feel at home there, while they're also pursuing the goal of using few resources.
I don't know how that impacts which dependencies are being used, but there probably is an impact.
LXQt kind of lets you choose what window manager you want to use inside of it. See "Which compositor is used?" and following questions in the link above.
I don't believe, it comes with a NightLight feature out if the box, but there's probably sone standalone application for that.
And well, whether its app menu is good, that's certainly a matter of taste. It's definitely serviceable, as far as I remember, but it doesn't have the amazing search of Plasma, for example.
I did. Looked at the desktop and it looks horrendous. pcmanfm-qt is the only usable app (and I find it second best filemanager after dolphin).
Their packages are supposedly very outdated on Fedora, which I didnt verify. And using Ubuntu base is a nogo for irrational reasons.
On Fedora they still rely on tons of Qt5 just like Plasma, which I find unacceptable.
Also I never used a Desktop where compositor settings are simply unsupported. It may run, but you still need config files, and I wonder why use settings then.
I really dont need so switch, KDE is awesome. It is not a pain anymore since plasma 6, Fedora Kinoite is very well maintained, Flatpaks work well, it has the best app support of all, legacy support, theming, cursors.
Its literally just for the curiosity.
I have a spare SSD where I try COSMIC too. Its tiling is usable thanks to some random dude that joined Fedora and created a SIG 2 months or so after that and now packages all the apps (He added drag to tile support). Thanks btw.
But it looks pretty ugly, it mimics the useless GNOME top bar, the app menu is kinda bad, so you would need to write at least 2 applets and replace the preinstalled ones.
Not a dealbreaker, and it works really good.
Yeah, LXQt is certainly a matter of taste. They introduced Qt6 support with the recent 2.0 release, which might not yet be on Fedora. You can also set its theme and icons to look like Plasma, although it's still not as consistent.
But yeah, if you don't care for LXQt's applications, you might rather like to try a minimal window manager, where the configuration is done via config file and the panel etc. is mostly DIY.
Although, it certainly still does not sound to me like you'd prefer it over KDE...
Haha no not really.
I look forward to pure Rust COSMIC, which works pretty well. But they need to do so much ground work, and their UX (overview, app menu, ...) is in parts pretty ugly.
I wonder what the best alternative to KWin is. Wayfire? Labwc?
Well, I haven't tried any of them. Apparently, LabWC is built to work similarly to Openbox, which I used before switching to KDE Plasma.
Openbox could do most things that Kwin could, although it had some big omissions, like no way to tile a window by dragging it to the screen edge (you could set up a keyboard shortcut to resize and move a window, though).
According to the LXQt link above, it also doesn't have desktop effects, if you want/need those.
But yeah, I know nothing about Wayfire...
And that was back when both used XOrg to do the heavy lifting.
Wayfire is used in a lot of minimal desktops. Raspberry PiOS uses it for their new Wayland desktop.