Hello everyone, this version is special not only because of the new features, but also because for the first time someone has contributed to the code. This may seem trivial, but it is important to me and to the project, as it means that people like it and it will continue to grow over time
Djmenig, I don’t know if you will read this, but thank you for your time and for your interest in making Fluid Tile better
Features
- Auto-switch layout based on tile count made by djmenig This new feature allows you to choose whether you want to add new desktops or switch to the next available layout with the default layouts, avoiding the creation of new desktops
- Add “Trigger overflow per screen”, only works when “Switch to next tile layout” is enabled
Improvements
- The trigger that displayed the UI is now more accurate
- The QML object
Timeris created dynamically and works independently - Simplified the tile assignment process
- Preventing signals from other windows from being disabled in certain processes
- Maximize trigger simplified
That’s all, remember that you can support the project by adding your ideas, reporting errors, or making pull requests, as well as inviting me to a “ko-fi”
Have a nice K-day!!!
I haven’t tried polonium, so I don’t know how it works. If you have any problems or questions, don’t hesitate to ask me
it had kinda the same idea of working with kwin instead of against it but it just worked worse than other options. iirc it got abandoned bc nobody was interested anymore once krohnkite was revived. yours also seems kinda similar to mousetiler.
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.
what’s the issue though? the existing system in plasma is already so out of the way its barely useful, so it makes sense to replace it with a better system and just ignore it. not that you shouldnt be doing what you’re doing, I just dont get why.
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.