You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
As we've learned in #18 and in various comments, this script can be fairly confusing, especially for users new to tiling.
I propose (and will probably also implement, but anyone reading this feel free to help) to create more/better documentation and to do it in one place. Since I don't have any actual site of my own, I'll probably do it here on github, and the README.org is a good start.
So, what needs to be documented?
An introduction to tiling
The various layouts
The resizing functionality
The various hotkeys
The concept of the "master" window
The text was updated successfully, but these errors were encountered:
Yes, documentation would help. I have not been a tiling WM user in the past, though I have become interested in tiling. I have looked at i3 and Sway, but don't really want to switch away from Plasma. I haven't needed a cheat-sheet printed out since the 80's... but i3/Sway take getting used to. Adding tiling features to KWin with this script sounds like exactly what I am looking for. But how to make it work? Even some simple docs, or a link to a YouTube or Vimeo video giving an overveiew would be very helpful and appreciated. Consider this my Plus-1 or up-vote. Thanks!
Also explicitly mention when to expect it to become effective. Specifically, would this be once the install is complete or is a restart of plasma required?
As we've learned in #18 and in various comments, this script can be fairly confusing, especially for users new to tiling.
I propose (and will probably also implement, but anyone reading this feel free to help) to create more/better documentation and to do it in one place. Since I don't have any actual site of my own, I'll probably do it here on github, and the README.org is a good start.
So, what needs to be documented?
The text was updated successfully, but these errors were encountered: