Some ideas about kwin-tiling HOT 3 CLOSED

Provide an option to set workspaces to have either a tiled/floating layout (i really have no idea if this can be implemented or not)

Already implemented, but the UI is not that great. The textbox below the excluded list contains something like "3:BladeLayout,1:HalfLayout,-8:". The numbers before the ":" are workspace numbers, and if they are negative, tiling will be disabled. What follows the ":" is the default layout (if empty, it'll use "HalfLayout", which is also the global default).

I've been dying to figure out how to expose this properly.

Like if the app is at the top of list, it will start as master and keep its position no matter what

Well, there's the option to choose starting new windows as master or slave, and if you start new windows as slave you can keep one as master indefinitely. I don't think we should stop the user from moving a window to another tile, and this would open up a can of worms with e.g. multiple windows that should be master (including multiple windows of the same class, e.g. two firefox windows).

Can you explain what this would be good for?

Add some space from screen edges too, as it does already for windows.

I don't quite get what this is good for, though I might add it if I have the time. The way I'd do it would be to have two separate "useless gaps" modes: The one we have now (gaps between windows), and gaps between windows and between windows and screenedges.

from kwin-tiling.

Already implemented, but the UI is not that great. The textbox below the excluded list contains something like "3:BladeLayout,1:HalfLayout,-8:". The numbers before the ":" are workspace numbers, and if they are negative, tiling will be disabled. What follows the ":" is the default layout (if empty, it'll use "HalfLayout", which is also the global default).

I've been dying to figure out how to expose this properly.

Oh, damn, i missed that textbox somehow :P
Tried: works like a charm.

Well, there's the option to choose starting new windows as master or slave, and if you start new windows as slave you can keep one as master indefinitely. I don't think we should stop the user from moving a window to another tile, and this would open up a can of worms with e.g. multiple windows that should be master (including multiple windows of the same class, e.g. two firefox windows).

That would be a problem, didn't think at it...
Well, haven't played that much with the script yet, i'll try to get used to the master/slave settings & shortcuts.

I don't quite get what this is good for, though I might add it if I have the time. The way I'd do it would be to have two separate "useless gaps" modes: The one we have now (gaps between windows), and gaps between windows and between windows and screenedges.

Mainly aesthetic reasons, actually. It's nicer to get margins to be applied on every side, instead of just being used as mere separators. This can easily goes as the bottom priority in your todo list eventually..Really: i'd like to see this, but it's not essential.

from kwin-tiling.

So, the first idea is already implemented (though the UI could use some love), the second is too difficult to implement properly (for now) and the third has been fixed by 54df571.

I'm closing this.

from kwin-tiling.