dots-hyprland VS PaperWM

My work on AGS, so far, has been mostly focused on adding support for additional features that weren't available before. I implemented the possibility to write your own PolKit agent in AGS and have just recently gotten secure session locking via the ext-session-lock-v1 Wayland protocol working. I still need to clean up the code and send PRs upstream, though.

That said, my config is available on GitHub [0]. If you want to see much more complete setups, you should check out the configurations by Aylur (creator of AGS) [1], kotontrion [2], or end_4 [3]. I'm sure there are lots more that are notable, but these immediately came to mind.

[0] https://github.com/Cu3PO42/gleaming-glacier/tree/next/config...

[1] https://github.com/Aylur/dotfiles

[2] https://github.com/kotontrion/dotfiles

[3] https://github.com/end-4/dots-hyprland

I am new to hyprland and want to learn to customize. Before making my own, I wanted to look and install other's configs to learn how they. So I found this dots git.

> What made you choose hyprland over sway?

The number of people talking about how great it was, while it's much more recent that sway.

Eyecandy is important to, so is flexibility: check https://github.com/end-4/dots-hyprland and you'll see very different styles made from the same hyprland that I use in "each window is fullscreen" mode.

But to stay with a desktop, you've got to integrate it to your workflow.

Pure insanity https://github.com/end-4/dots-hyprland/tree/main

I'm afraid you will need osu!supporter for that >! It's in the original post's image (blog post link in my reply) if you didn't notice, may check each branch for correct version, since it seems to include multiple rices !<

But with auto-tiling you need to place windows according to a pre-set configuration, it needs to fit whatever layout you want to go for and it needs to be able to resize the window without breaking the content. This works pretty well for libadwaita apps, but a lot of webapps seem to assume a certain minimum window size. Another issue is how to handle modal dialogues, where paperwm for example sets an override to ensure they're not attached to the main window. Should the settings window then be treated as a separate window and tiled, or should it be left floating above all others?

I like Gnome's simplicity, agree with most of its deviations from the tired old Windowsy desktop status quo, and am very happy to depend on all its great integration work. I can't quite live with the simplistic window management, but extensions cover that (as they do much else). With Fedora + Gnome + PaperWM, I'm quite at peace with the current linux desktop situation.

Still I'm looking forward for something like PaperWM to be possible in KDE - or even to write it by myself

I have noticed in one of your comments in this thread that you are looking for novel ideas of the UI look. As others commenters stated, you might be interested in tiling window managers like i3 [0] or sway [1]. They are truly a gem for productivity and sometimes for an eye [2].

However, I love the concept of scrollable window manager like PaperWM [3] is. When I had a smaller screen (24" 16:9) I was complaining a lot on unused space on my screen. With PaperWM I was finally happy with its dimensions, because I could have huge IDE on the left and small part of terminal displayed on the right. That way I knew if something was printed to terminal, while my editor took 80% of the screen.

[0]: https://i3wm.org/

[1]: https://swaywm.org/

[2]: https://www.reddit.com/r/unixporn/

[3]: https://github.com/paperwm/PaperWM

If you want something really different, give PaperWM a shot.

You may want to try PaperWM (GNOME extension) https://github.com/paperwm/PaperWM