• 9 Posts
  • 6 Comments
Joined 2 years ago
cake
Cake day: August 19th, 2024

help-circle
  • 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.


  • Mouse Tiler has the same problem as the other options: it replaces the KWin system.

    I recently added a compact mode for user interfaces similar to Mouse Tiler or Kzones, for those who don’t want the overlay to take up the entire screen.

    The fact is that they all follow the same pattern, replacing the KWin system, and I don’t think that’s the best option. In the end, conflicts will always arise because you’ll always be fixing incompatibility issues with two systems that are fighting each other.



  • Fluid tile does not replace the KWin tiling system, just adds more auto-tiling features. Krohnkrite and Karousel replace the current KWin tiling system

    Fluid tile works with KWin tile editor (Meta + T shortcut), this allows better integration with KWin without needing to create another tile editor as is the case in Krohnkite, additionally, you can use the shortcuts that come with KDE by default to move windows, and expands functionalities such as changing the tile layout with shortcuts, etc…

    The idea is to adapt to the KWin tiling system, not replace it