Live data from Hacker News

KDE Plasma Widget for external monitor brightness adjustment

github.com

61–65 of 65 posts

Re: KDE Plasma Widget for external monitor brightness adjustment

#61

Earlier quoted context omitted.

Developer here, why wouldn't you just install the official pip package `ddcci-plasmoid-backend`?

I personally avoid using pip for managing system libraries because they often end up conflicting with distribution provided packages. Even if packages are missing upstream, they often pull in dependencies that may end up conflicting later. Versions start mismatching, tools stop using when sudo gets involved, all kinds of weirdness that's hard to debug if it's caused by a library you pulled in months ago. My workaroun…

I get your point. At some point this widget provided an option to specify the backend command manually, though I removed it because I couldn't see any use cases. I would happily add this functionality again if you require it.

Re: KDE Plasma Widget for external monitor brightness adjustment

#62
post #28
post #26

Earlier quoted context omitted.

I've user Lunar for quite a while, then moved to MonitorControl, and am now on BetterDisplay, which notably includes DDC/CI over the M1 HDMI ports. Also its ability to fake screens of arbitrary resolutions e.g for headless machines is solid gold. https://github.com/waydabber/BetterDisplay

Yes, BetterDisplay got DDC support on HDMI M1 soon after its dev learned that I added it in Lunar: https://github.com/waydabber/BetterDisplay/issues/1361 I’m friends with Istvan (the BetterDisplay dev) from the time he was a Lunar user, and we usually share implementation details for non-Pro features.

I must concur with sibling comment by sausajez, and say thank you for sharing knowledge and code between the "competing" projects! I feel like everyone is better off this way.

Re: KDE Plasma Widget for external monitor brightness adjustment

#63
post #59
post #49

Earlier quoted context omitted.

I've tried setting up clight on various occasions and now gave it a shot again, whilst I appreciate all the documentation I'm still struggling to get it working on NixOS with swaywm on a laptop. I'm primarily interested in adjusting screen brightness based on my webcam. I'm already using redshift/gammastep.

Uh that's sad! There is actually an issue opened about NixOS; but, since I am not using it, it's pretty hard for me to debug. If you want some help you can comment on that issue though!

Thanks! Totally overlooked that. I've managed getting through the first hurdles last night, I'll leave some more feedback on GitHub :).

Re: KDE Plasma Widget for external monitor brightness adjustment

#64

Earlier quoted context omitted.

I personally avoid using pip for managing system libraries because they often end up conflicting with distribution provided packages. Even if packages are missing upstream, they often pull in dependencies that may end up conflicting later. Versions start mismatching, tools stop using when sudo gets involved, all kinds of weirdness that's hard to debug if it's caused by a library you pulled in months ago. My workaroun…

I get your point. At some point this widget provided an option to specify the backend command manually, though I removed it because I couldn't see any use cases. I would happily add this functionality again if you require it.

I was just explaining why people like me don't like using pip as a system package manager, I'm not trying to turn this into a feature request :)

I have my solution and I think many others have their own. In my opinion it's perfectly fine to just state "platforms that don't have the necessary packages in their system package manager aren't supported, use at your own peril" so niche distributions making up the long tail of your users don't end up taking unreasonable amount of support and development time.

Re: KDE Plasma Widget for external monitor brightness adjustment

#65
post #22

If your distro doesn't have a package for the backend of this plasmoid yet, it invokes the backend with[1]: python3 -m ddcci_plasmoid_backend So you can probably get away with this: git clone https://github.com/davidhi7/ddcci-plasmoid \ && cd $(python3 -c "import site; print(site.getsitepackages()[0])") \ && ln -s $(cd -)/ddcci-plasmoid/backend/ddcci_plasmoid_backend . [1]: https://github.com/davidhi7/ddcci-plasmoid/…

Developer here, why wouldn't you just install the official pip package `ddcci-plasmoid-backend`?

I never use pip for the system site-packages, that's the job of the distro package manager.

As for pip install --user, I sometimes nuke the local repo so wouldn't be a robust solution given my workflow.

Post reply on HN