However, before i proceed to try it, i’d like to ask the opinion of experienced kdelinux devs & users pls? Would it cause any foreseeable conflicts in kdelinux? Any apparent safety implications?
Historical posts on Shading, but not this project:
In principle the basic pattern (KWin scripts interacting with a user DBus service) is fine in KDELinux.
However, the code as it is now won’t “just work” on KDE Linux. It assumes that the PyQt6 Python libraries are available at the system level, which in KDE Linux they aren’t. On a “traditional” distro they could typically be installed through the package manager (e.g. in Fedora sudo dnf install python-pyqt6). But on immutable distros the best way to do it would be to create a virtual Python environment.
It’s possible to set this up locally oneself, but I would be interested in whether the developer wants to provide it as an install option.
A more trivial point is that it would be easier to use to ~/.local/bin (which should be on the PATH by default in KDE Linux) as the installation location rather than the default ~/bin, but it looks like that’s easily settable at install time.
Nothing seems concerning in the code from a safety / security perspective.
Thank you very much for explaining the necessary steps [i am not knowledgeable enough to have been able to discern this myself from the clue kindly provided earlier by @pg-tips ]. However i’ve decided not to proceed with this. I do not wish to use PIP, for potential security reasons due to its unpleasant history afaict… & i am not skilled enough to be able to know what to do to adequately protect myself if i did use it.
So, as it turns out… still no shading for me, alas.
