From kwin  Thu Mar 22 06:34:14 2012
From: Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= <mgraesslin () kde ! org>
Date: Thu, 22 Mar 2012 06:34:14 +0000
To: kwin
Subject: Re: Re: Re: [GSoC] KWin colour management
Message-Id: <8826913.ga5CULkvRM () martin-desktop>
X-MARC-Message: https://marc.info/?l=kwin&m=133239814803750
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1849762336785779729=="


--===============1849762336785779729==
Content-Type: multipart/signed; boundary="nextPart2416849.kJJix6Lg60"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: quoted-printable


--nextPart2416849.kJJix6Lg60
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Thursday 22 March 2012 07:02:27 Kai-Uwe Behrmann wrote:
> Am 21.03.12, 20:34 +0100 schrieb Martin Gr=C3=A4=C3=9Flin:
> > I think you do not know how KWin's rendering works. In a simplistic=
 way: a
> > window is rendered to the screen through a shader. At runtime KWin =
decides
> > which shader to be used. As by that there is always only one active=

> > shader, so to have color correction it has to be added to all shade=
rs
> > which render windows/textures/colors.
>=20
> Thanks for the description.
>=20
> > This is different to any experience you might have from Compiz 0.8.=
 There
> > the screen was not rendered with shaders but plugins could use shad=
ers.>=20
> >>> Do you have any references showing that it is impossible to add c=
olor
> >>> correction to Qt during the lifecycle of Qt 5? I'm sorry, but I d=
on't
> >>> base
> >>> technical decisions on "my feeling says".
> >>=20
> >> That would mean colour management appears earliest inside Qt 6. Bu=
t it is
> >> at the moment not clear if that happens at all.
> >=20
> > Any proof for these bold statements? Anything from Qt where I can s=
ee that
> > this is the case (also for Wayland)? Remember nobody wants to devel=
op for
> > X
> > anymore ;-)
>=20
> As we discuss a equivalent of colour management in KWin, we talk abou=
t
> default colour management of all displayed Qt widgets. That is a high=
 goal
> and likely coming with some API changes. Such changes need quite some=

> preparation.
> What signs are visible that with the first release of Qt 5 will have =
full
> CM? Even if people would put CM now high on the Qt develpers or simil=
ar
> agendas, CM will likely not get included soon to be ready for the fir=
st
> Qt 5 release. Then logically the next feature window is Qt 6.
Sorry but I don't follow that logic. Just because it won't make it into=
 5.0=20
(which is impossible) does not mean that it won't enter any 5.x release=
.

And that's what I asked for: is there any reference stating that it won=
't be=20
possible to add CM to Qt in the lifetime of Qt 5?

Cheers
Martin
--nextPart2416849.kJJix6Lg60
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAk9qx+YACgkQqVXwidMiVrp7xwCcDSm5LDorJCK/X0y2Dar0Iuga
/LIAnjspetfK7Iv1AOhQ3tX0GY7xLcrS
=17UU
-----END PGP SIGNATURE-----

--nextPart2416849.kJJix6Lg60--


--===============1849762336785779729==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin

--===============1849762336785779729==--