Open msrsaditya opened 10 months ago
Sway is an i3 clone. i3 follows manual tiling. I think this is outside of the project goals.
That's why I raised this issue in swayfx, because this is not an i3 clone.
It's the fork of an i3 clone. I think you're better off using a dynamic tiler. Maybe will can give a more clear answer regarding the project goals.
They're not mutually exclusive though are they? It could always stay manual tiling by default. AwesomeWM actually has an interesting concept which allows you to set the initial floating, tiling, tabbed or other modes by workspace.
I think the main question is can an extra tiling mode be implemented in such a way that does not break sway codebase compatibility. I would agree that anything that breaks importing sway commits is a problem.
@msrsaditya in the meantime you can use projects like
https://github.com/nwg-piotr/autotiling
to do autotiling outside of the wm.
Already using it, I just wish it comes baked in in a wm like sway, it's not possible with that so I raised this issue here:)
Feature Request: