From kde-panel-devel  Thu Apr 09 15:06:01 2015
From: Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= <mgraesslin () kde ! org>
Date: Thu, 09 Apr 2015 15:06:01 +0000
To: kde-panel-devel
Subject: Re: KGamma and Plasma
Message-Id: <1760477.2ZqzGlT3Px () martin-desktop>
X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=142859198307322
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============8926157367899070762=="


--===============8926157367899070762==
Content-Type: multipart/signed; boundary="nextPart1905544.bUfBJi49K1"; micalg="pgp-sha1"; protocol="application/pgp-signature"


--nextPart1905544.bUfBJi49K1
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"

On Thursday 09 April 2015 16:29:05 David Edmundson wrote:
> A while back I ported kgamma to KF5, which is in a branch somewhere.
> 
> It's currently being released with applications, which doesn't really make
> sense as it's a KCM. As far as I can tell the main author is inactive.
> 
> We have two options:
>  - move kgamma to kde/workspace for Plasma 5.4
>  - merge the code into plasma-desktop with the other kcms
> 
> I'm torn as on one hand I don't like having a lot of repos for tiny things
> on the other gamma adjustment really isn't an essential thing, and I like
> having a core -> extra stuff split.
> 
> It seems a month ago Lukas ported colord-kde, as I understand it these two
> do basically the same thing but with competing implementations. So maybe
> there's a 3rd option of going with that. The main author on that also seems
> to have been inactive in that repo for a long time.

I wouldn't call it competing implementation, just a different scale. colord 
gives better results than kgamma if it works, if not kgamma is better than 
nothing.

Given that it would be awesome if we could figure out whether colord is 
properly supported and then show colord, otherwise kgamma. Does that sound 
possible?

Anyway I'd say both are candidates for plasma-desktop.

Oh and yes there is the 3rd way which is hooked up with KWin's color 
correction. But that is such a weird setup that I still haven't succeeded with 
setting it up at all.

Cheers
Martin
--nextPart1905544.bUfBJi49K1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEABECAAYFAlUmlWMACgkQqVXwidMiVrpKHQCfdADzcyFNyOBVGvXHt7upSHL7
34MAoKVZOp3UVTMWGTSdj2VvNXpiTdNs
=jCiN
-----END PGP SIGNATURE-----

--nextPart1905544.bUfBJi49K1--


--===============8926157367899070762==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUGxhc21hLWRl
dmVsIG1haWxpbmcgbGlzdApQbGFzbWEtZGV2ZWxAa2RlLm9yZwpodHRwczovL21haWwua2RlLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3BsYXNtYS1kZXZlbAo=

--===============8926157367899070762==--