Feature request: dynamic SnapToEdge sizing about labwc

[tsujan]

Describing my opposite point of view:

When the feature requested here was implemented in KWin (recently), it was annoying to me because I relied on the window size after snapping, and the only way to restore it was logging out and in and avoiding resizing of snapped windows (which I did a lot before).

[Consolatis]

This goes quite a bit into the "tiled window manager" direction. The issue I see with this is that it would only work for 2 windows per direction. It is also not clear how this would work if you have multiple stacked windows on top of each other that are all snapped to the same output edge.

[Vladimir-csp]

This goes quite a bit into the "tiled window manager" direction. The issue I see with this is that it would only work for 2 windows per direction. It is also not clear how this would work if you have multiple stacked windows on top of each other that are all snapped to the same output edge.

Perhaps it would set size for two snapped regions on workspace (left+right edge or top+bottom edge), so any window that is snapped to that edges on workspace would be affected.

the only way to restore it was logging out and in

An action to restore horizontal or vertical edge snap border position?

[tsujan]

An action to restore horizontal or vertical edge snap border position?

Possible.

But, frankly, I'm getting a little worried. LabWC is very stable and lightweight. For keeping it so, adding of new futures may need to be limited to the most useful or popular ones. Not setting a limit for new features might result in a chaos.

Of course, I'm not a developer of LabWC — I'm only a user of it — but I said that based on my experience as a developer in in other places.

[Consolatis]

For keeping it so, adding of new futures may need to be limited to the most useful or popular ones. Not setting a limit for new features might result in a chaos.

That sums it up pretty good. I'd add to that that some features can be provided in a way that allow for multiple usage patterns but others simply can not be provided this way or would introduce massive complexity in the codebase when doing so which in turn makes it harder to maintain / enhance labwc in the future.

Then there is also the user expectation aspect, if we were to implement something like requested here users may then end up choosing labwc for this feature because it fits their expectations but related expectations are not fulfilled (e.g. more than 2 windows in each direction, separate sizes per workspace, a set of "layouts" which can be cycled through, "dynamic tiling" and so on).

At the current point I'd say that labwc adding this feature is unlikely.

[johanmalm]

This is out of scope.

Can be done with regions and a client. I did some prototyping a while ago: https://github.com/johanmalm/labwc-regions