What algorithms does this project use for managing layout? about kwin-tiling HOT 3 CLOSED

Well, the strategies are layout-specific - the main tiling class just hands the number of clients that are to be tiled to it and then applies those results, in order. See contents/code/*layout.js. For example the default "HalfLayout" (stupid name, I know) makes the first window fill the left half of the screen and divides the right half evenly between the rest (higher index -> lower), while "BladeLayout" divides the screen evenly between all windows along the x-axis (i.e. every window gets width = screenwidth/x)

Or am I not understanding you?

(Oh and FTR, I'm thinking of simplifying layouts further)

from kwin-tiling.

I guess if you stick to simple layouts like you mention there's no need for any special algorithms. However, I guess the problem of laying out windows in tiling manager in general case is not simple. Some interesting behavior could be seen in video of Siemens' RTL for example.

What do you mean by simplifying layouts further? What's not simple now?

from kwin-tiling.

Some interesting behavior could be seen in video of Siemens' RTL for example.

Seems like halflayout and bladelayout already do something like that.

What do you mean by simplifying layouts further? What's not simple now?

Well, halflayout.js is 321 lines long, so "simplifying" the code, not the layouts themselves.

Mainly, I'm trying to unify the code used by layouts by moving more into the base class (layout.js), like it already handles switching resolution/area. Ideally I'd like tile resizing to be implemented once so that it can be used by all layouts (including spirallayout, which currently doesn't do resizing at all), but I haven't quite gotten it right. If you have some sources on how to do that, I'd be happy to look into it.

from kwin-tiling.