Hi, I have good news for those who use a tilling system. I have been working these month on a new system for Fluid tile with the aim of making it easier to maintain and more reliable when moving your windows
During the rewrite, I had to discard some user options that increased the possibility of a error. These options did not add any real value, and I preferred to prioritize reliability of the script
Features
Shortcuts
-
Fluid tile | Toggle window to blocklist: Disables the window that is active or has focus so that it does not interact with Fluid tile. If the application name was already included in the block list in the user configuration, the list will take precedence over this shortcut.
-
Fluid tile | Change tile layout: Change the layout of the tiles and rearrange the windows
You can change them in the system settings
https://codeberg.org/Serroda/fluid-tile/wiki/Shortcuts
Breaking changes
WindowExtendTileChangedDelay now by default is 300, change in your user settings with this value
Now, windows will always expand when possible, the UI cannot be disabled, and whenever you move a window to a tile that already has windows, they will always be swapped
These variables will stop working:
WindowsOrderMove
WindowsExtendOpen
WindowsExtendClose
WindowsExtendMove
WindowsExtendMinimize
WindowsExtendResize
UIEnable
I recommend you take a look at the wiki where it will clarify your doubts
https://codeberg.org/Serroda/fluid-tile/wiki
One more thing, this time the news isn't so good
Since my laptop keyboard broke (for whatever reason, neovim doesn't work well without a keyboard /s), I don't have the money to repair it right now, and I have to study for my firefighter exams, there will be fewer updates to the script in the coming months
I encourage you to try it out and let me know what you think. If you find any errors, you can report them in the repository
https://codeberg.org/Serroda/fluid-tile/issues
Have a nice day!
Edit: Demo video https://youtu.be/SKre99-ud-U
These projects are like patches to cover up something you don't like to see. Replacing the system would mean collaborating on the KWin code so that future versions improve, and none of these options do that. In the end, KWin will release an auto-tiling system, and it is doing so slowly. Perhaps it will adopt Fluid Tile as an option, since half the work is already done.
The same thing happened with SDDM and plasma-login
KWin will evolve and is here to stay. Creating a script that covers up things you don't like will only result in the script becoming outdated over time.
It's like if you have damp on a wall and you try to cover it up with a picture. The damp will continue to grow if you don't fix the wall from the inside, and the picture will stop covering the damp and will no longer serve its purpose.