Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Explain configuration menu #18

Closed
Keks-Dose opened this issue Apr 30, 2014 · 5 comments
Closed

Explain configuration menu #18

Keks-Dose opened this issue Apr 30, 2014 · 5 comments

Comments

@Keks-Dose
Copy link

I'm looking for a simple way to resize a window to the size of half of the screen and to move it to the left or to the right side of the screen, so that I have two windows which fill the screen fully. Works in Windows: Windows-key + arrow left /right. I'd really like to have those shortcuts as well in KDE, and probably many other people would like that as well. So your script probably offers something valuable. Unfortunately it lacks of documentation a bit.

I installed kwin-tiling and went to the configuration menu. I understand that I can add in the first line some programms which will be ignored by kwin-tiling. But there is a second line, where I could add text, if I knew to which purpose?!

And what is the meaning of "Start As Master"?

In the last line of the config is a "0", but I can insert e.g. 15. Could you explain the purpose of that line as well?

I really appreciate your script, but as a more or less dumb user I need documentation, pleeeeaaaase. And when you are on it, could you give me a hint how to get Windows-key plus arrows left / right as shortcuts to arrange two windows side by side?

Thank you!

@faho
Copy link
Collaborator

faho commented Apr 30, 2014

I'm looking for a simple way to resize a window to the size of half of the screen and to move it to the left or to the right side of the screen, so that I have two windows which fill the screen fully. Works in Windows: Windows-key + arrow left /right. I'd really like to have those shortcuts as well in KDE

For that you don't actually need this script but just the kwin built-in "quicktiling", which you can also bind to a hotkey - the german name (which I'm guessing might be of use to you) is "Fenster am linken Bildschirmrand anordnen" etc.

As to the rest...

I understand that I can add in the first line some programms which will be ignored by kwin-tiling.

Yes, these are windows that are ignored, identified by their so called "class". Ideally I'd like to hook this up to kwin's rules system, but this has served the purpose rather well so far.

But there is a second line, where I could add text, if I knew to which purpose?!

This is... a placeholder, really, until I can figure out how to do the UI properly.

This is a line that defines what tiling layouts are set up on what desktops, and also if tiling is enabled by default on a per-desktop basis. The syntax is "$DESKTOP:$LAYOUT,$DESKTOP:$LAYOUT,...", where a negative desktop will indicate inactive tiling (by default).

And what is the meaning of "Start As Master"?

Every layout can define a "master" window, which is usually the biggest one (for the default layout, it's the one on the left). If this is enabled, new windows will be moved to that position, if it is disabled, they will be put at the end.

In the last line of the config is a "0", but I can insert e.g. 15. Could you explain the purpose of that line as well?

That's the size for gaps between windows.

Unfortunately, all of these options require a script restart (or a full kwin restart) to update.

@Keks-Dose
Copy link
Author

I'm looking for a simple way to resize a window to the size of half of the screen and to move it to the left or to the right side of the screen, so that I have two windows which fill the screen fully. Works in Windows: Windows-key + arrow left /right. I'd really like to have those shortcuts as well in KDE

For that you don't actually need this script but just the kwin built-in "quicktiling", which you can also bind to a hotkey - the german name (which I'm guessing might be of use to you) is "Fenster am linken Bildschirmrand anordnen" etc.

Oh, surprise, should have known earlier... Thank you very much!

faho added a commit that referenced this issue May 3, 2014
@faho
Copy link
Collaborator

faho commented May 3, 2014

Soo... I'm not sure if you're still interested in using the script, but could you take a look at this: Image and tell me if it's better? I'm still figuring out the per-desktop configuration, though.

@Keks-Dose
Copy link
Author

Ooops, sorry for the delay. Yes, this is a step in the right direction. Now one can see what the last field is for: the gapsize, maybe you add "between windows". Well, I'll play with future versions of your script, but honestly: I'll be much more interested, if I know how the script is intended to work. So make a break in coding and write docu with some pictures to explain the different layouts, the function of a master window, your shortcuts and so on. I only can offer to act as the DAU who proofreads the docu.

@faho
Copy link
Collaborator

faho commented May 7, 2014

the gapsize, maybe you add "between windows".

I've changed it to "Size of gaps between windows" now.

So make a break in coding and write docu with some pictures to explain the different layouts, the function of a master window, your shortcuts and so on.

Interesting thought. Previously, I've always had this idea in the back of my head that this script will mainly be used by people who have previously used tiling window managers and then switched to KDE/Kwin (I'm fairly excited for lxqt, and have been testing the script with razorqt). As I've now learned (via your comment here and another on kde-look.org), there are actually people who may use this as their first tiling window manager.

Now, the most pressing problem I have is... how do I get the doc to the user? As far as I know I can't ship anything substantial with the script (or at least not beyond just putting it in the .zip and tell users to look on some hidden folder in their $HOME), so it may only be possible to put a link to this site in the description.

Well, I think this bug is pretty much done (if not tell me) and I'll be opening a new one for documentation.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants