Closed tyush closed 1 year ago
Wouldn't something like https://github.com/nwg-piotr/autotiling be a better fit rather than complicating the already complicated Sway layout code? @WillPower3309 any ideas?
Wouldn't something like https://github.com/nwg-piotr/autotiling be a better fit rather than complicating the already complicated Sway layout code? @WillPower3309 any ideas?
Yeah, generally we only accept things that aren't possible with the sway ipc. I've mostly focused on the rendering side where position and size are known, but that said, if there's an easy and minimal way to support other layouts I wouldn't be opposed to the idea! I just don't know if it can be done in such a way
Wouldn't something like https://github.com/nwg-piotr/autotiling be a better fit rather than ...
Ah, I hadn't seen that tool before; it appears to do exactly what I was describing in the request. Thanks!
Although a pretty far stretch, alternate partitioning schemes for window space, such as bspwm's binary space partitioning, would allow for more efficient usage of screen space based on a user's preferences. Sway already has support for nesting schemes through
splith
andsplitv
, turning a window into what's effectively a "nested workspace", able to use a different scheme than it's parent. This enhancement would ideally allow for a strategy defined in a user's config for where a new window should be placed, potentially splitting an existing window.Wishlist for strategies: (number is order windows were created, 1 being first) Binary tree (latest window region is split for new window)
Inverse binary tree (newest window is given half of the screen)
Rectangular (prioritizes maintaining aspect ratio)
Horizontal (newest window is given half the screen, splitting the screen between the window and the rest of the windows arranged horizontally)