[Openicc] xrandr output properties / icc profiles

Tomas Carnecky tom at dbservice.com
Wed Jul 16 03:30:19 PDT 2008


Kai-Uwe Behrmann wrote:
> Agreed, the syntax must be clear about profile to Xinerama or whatever 
> mappings. The current Xinerama syntax required in the specification will 
> shurely be extended at some point.

I don't think that Xinerama will be developed any further. XRandR 
replaces all of its functionality and adds even more features (xrandr 
can be used to configure the hardware whereas xinerama can not).

See this document: 
http://gitweb.freedesktop.org/?p=xorg/proto/randrproto.git;a=blob;h=6719cf800a93a346d82514fc035b4f05cd27792e;hb=2df8499d24d15bfca3c928b681f64b6e8a05f0af;f=randrproto.txt#l1164

>> With XRandR V1.2 and output properties there is no such ambiguity.
> 
> XRandR V1.2 is ambiguous itself. Who says XRandR will be the last? In five 
> years we probably see the next evolutionary step. 

I don't think properties will be going away anytime soon. The xserver is 
now adding properties to input devices as well. So pretty much any 
'object' inside the xserver can now have properties. Properties are a 
generic mechanism to extend existing functionality.

tom



More information about the openicc mailing list