[Openicc] ICC Profiles in X Specification 0.4

[Richard Hughes]

On 24 March 2010 17:03, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
> I can see that it would be beautiful if we had working XRandR right from the
> beginning. But practical sense tells me that applications break if the spec
> up to version 0.3 is ignored.

XRandR works on all my hardware I have here. I've got laptops with
radeon, nvidia and intel hardware all working well with XRandR and
KMS. This is on Fedora 13. More importantly XRandR is setup by default
and all the graphical monitor configuration tools are using XRandR,
not Xinerama.

> We see applications, which support multi monitor setups. So one ICC profile
> alone, the root window _ICC_PROFILE one, is not enough information for them.

Sure, I agree.

> Applications have a advantage to directly render into monitor device space.
> This is known as early or application side colour binding.
> Reasons might be to get more control about buffer formats and the rendering
> process.

Can you give examples?

>>> _ICC_DEVICE_PROFILE by the colour server at run time. Apps supporting the
>>> per window region communication can use that _ICC_DEVICE_PROFILE atom(s).
>>
>> I don't think that makes sense at all.
>
> The proposed changes where implemented quickly and work as expected:
> backward compatible, with as few as possible limitations and highly
> flexible.

Right, well, with the current changes I don't think GCM is going to
ever support anything higher than 0.3. GCM is already set to be
installed by default for Fedora 13, and I'm guessing that's quite a
few million users who will be stuck with an old implementation. I
don't want to sound like an ass, but if you just change the spec to
add features to oyranos without outside peer review then that's not
exactly working on a shared "specification".

Sorry to be blunt.

Richard.