(02-10-2020, 05:05 PM)ckester Wrote: Along with the popular vertical stack, other "layout strategies" per your definition include:
- fibonacci or "spiraling" layout, where each additional pane is smaller by a golden ratio
- dividing current pane in half (without the notion of a master window as in the vertical stack layout)

Yes. The fibonacci one is also something I remember having seen, looks nice on paper, but it's probably horrible in daily uses, except if someone have a screen big enough maybe?

(02-10-2020, 05:05 PM)ckester Wrote: I'm partial to the vertical stack layout myself -- although I sometimes wish I could put the master window on the right when I'm working with two side-by-side monitors, so that the master window on each monitor would be "next" to the other, if that makes sense.

I think a proper layout support can be useful. I3 have such thing IIRC, but last time I gave it a chance, it really felt like a quick hack or workaround.

My layout depends on what I'm doing. Even with my current shitty screens, when I code I like to have at least 2 windows per screen, and since I use C or C++ most of the time, I often end up with 3 or 4: 1 "major" implementation on which I work, optionally it's header, and then the code that calls it, or which is called by, with the header.
Alt screen is usually reserved to communications, monitoring, build logs, and manpages. At least, this is when I write code.
When I debug, well, it depends on what I debug, things can go pretty ugly when one needs to play with 3 processes to find a problem :)
Then I also use a different layout when I'm playing the admin, but I can hardly say it's fixed yet: I still am trying to learn to use new tools (and to understand how they work, with which techs, so that I really understand their up and down sides. This is why I'm still not playing with LXC/docker for example: I want to master cgroups and namespaces before, and one of linux's MAC systems).
I suppose when I'll know my tools, a layout will emerge by itself.