[Openicc] xrandr output properties / icc profiles

[Kai-Uwe Behrmann]

Am 15.07.08, 09:19 +0200 schrieb Kai-Uwe Behrmann:
> Am 15.07.08, 11:12 +1000 schrieb Graeme Gill:
> > Tomas Carnecky wrote:
> > > Have we agreed on a naming convention for xrandr output properties? 
> > > Also, are there any tools that can load ICC profiles into xrandr 
> > > outputs? I had a brief look at argyll, it has code that reads the 
> > > EDID_DATA output property, but it doesn't seem to support profiles 
> > > attached to outputs. Oyranos doesn't have any xrandr code AFAICS.
> > 
> > Argyll V1.0.0 "dispwin" sets the _ICC_PROFILE property in XRandR V1.2 output.
> > Grep for XRRChangeOutputProperty() in the source if you want to locate the code.
>  
> _ICC_PROFILE would be fine. Still I have no system to check a 
> implementation.
> 
> I will try to setup a proper system in the next days for checking a 
> appropriate implementation in Oyranos.

Given my recent test on a system, which does not support xrandr in the 
driver I would pretty outrule the direct output property path.

* output properties are dependent on the driver implementation as we 
  lerned, thus they are flacky supported, as I could experience
* they add easily another pice of complexity to the ICC Profile in X spec
* a client is not required to know about XRandR, so a accordingly set 
  profile might be invisible, which is clearly inacceptable

I'd rather invest on, how to continue in setting the profile on the root 
window and give additional hints about the Xinerama and XRandR output 
mapping. This would be a more relyable base for a specification.


kind regards
Kai-Uwe Behrmann
-- 
developing for colour management 
www.behrmann.name + www.oyranos.org