Stacking windows instead of endless splitting

+1

I understand that having too many small windows in auto-split mode is annoying. Window stacking is a solution, but how to stack them is a complex algorithm. It's not just based on the number "n", but also needs to consider window sizes, whether space can be compressed. I'll think about how to optimize it.

When I have a lot of windows open, I usually spread them across multiple "Desktops (Spaces)". You can easily move windows to different spaces with keyboard shortcuts.

@1050424691510222908 Would it simplify to allow the user to define layouts (2x1, 2x2, etc.) with default rules (new windows go to stack N), per app overrides (chrome goes to stack N), and simple scripting (chrome goes to stack N unless condition)?

Default rule should probably be 1. Fill empty zones, 2. If all zones full, user option to go to zone 1 at top or bottom of stack versus overlay oldest window

Pre-configuration is too complex for users. What I'm considering is adding a layout mode called master-stack layout. The master window is on the left, and all the windows on the right are stack windows, which can overlap. Aerospace uses this layout, but its handling of window overlapping is not very good either.

I get that. One of my major gripes with most WM apps is their handling of presets. Hard to get it right and the definition of right is SUPER subjective

Indeed, everyone has different ideas. My design principle for presets modes is to keep them simple and intuitive, people don't have much patience.

I agree about presets. As someone who doesn’t mind doing the prep/work, I’ve come to see them as a kind of living paradox: no matter how easy or convenient they are, they eventually become stale.

About the master–stack layout: what about a BSP–master–stack hybrid?

Start with a BIG window (taking either half/third/quarter of the screen). From there, keep splitting and populating until you reach window n. At that point, reverse direction and start stacking: if a window fits in the current area, stack it there; if not, try the next area, working your way back toward the initial BIG window.

This might not be ideal for everyone, but with a large enough screen it could very quickly create a layout that roughly balances priority against available space. You could cycle through stacks, and—when sizes allow—swap the current/top window of a stack with another stack or with one of your master (primary or even secondary) BIG windows.

Just a thought

There was a time when I used the master-stack layout in Aerospace, and I found it to be quite practical.
That said, I think simply introducing the ability to switch between BSP splitting and stacking for the currently focused window would provide sufficient convenience.

This idea is clear and should be fairly easy to implement. It essentially means adding a third layout option for a BSP node, horizontal, vertical, and a new option: stack.

That's right.
In addition, I think we need to add “Forward” and “Back” to the focus and move shortcuts.

If "forward back" means "redo undo", that would increase the shortcuts from 4 to 6, adding unnecessary complexity in my opinion.

I'm sorry, I didn't explain that very well.
I'm referring to the operation that swaps the front and back of stacked windows.

The tab layout is a great idea.
The operation of swapping the front and back of the stack can be replaced by swapping the left and right sides of the window.

or swipe while holding modifier key or just 3 | 4 fingers

+1

You can currently drag tabs to rearrange them, but swapping windows in stack doesn't seem like a frequent need. The cmd-tab or directional focus shortcuts should be enough for quick window switching.