PaperWM VS i3

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

While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:

https://github.com/i3/i3/issues/4353

> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).

Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393

It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."

It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.

But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.

The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.

Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.

for example, take i3. https://github.com/i3/i3/issues/4478

For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it