Open silverhook opened 11 years ago
The choice around the KWin script begun when there was a discussion with the kde developers that a plasmoid shouldnt be able to handle window previews. For window previews only a kwin script was the best choice that time. In its current state (version 0.4.x) the plasmoid supports window previews but it is a very nasty workaround in order to do so. In a second communication with the developers I arose the question how the window previews will be handled from the taskmanager in Plasma Frameworks 5. There was not a spesific approach at that time.
So the only thing that remained was to implement both a plasmoid and a kwin script in order to able to be ready for the Plasma Frameworks 5 world. The plasmoid is very important also because it provides the same functionality to old hardware machines that do not support 3D effects.
These days either way I can only support only one of them. So I will stay focused in the plasmoid and wait in the future to see the development choices from the kde developers
Thanks a lot for the support....
OK, thank you for explaining this and that you keep developing it! I'm looking forward to the new versions! :smile_cat:
From what I underdstand, it would make more sense to drop the KWin script for WorkFlow and just implement those things into a full-screen plasmoid like e.g. login/lock screen.
Is there any reason why the need for a KWin script? In a discussion I had at Akademy, KDE devs told me that KWin scripts aren't meant for such behaviour, but recent Plasma should be completely capable of what you're trying to achieve (and if not such new features can and should be added to Plasma).
P.S. I thoroughly enjoy using WorkFlow. Thank you :]