[Openicc] Linux CM ideology, was: meta data in test chart

[Kai-Uwe Behrmann]

Am 04.02.11, 15:29 -0000 schrieb Richard Hughes:
>> Generic APIs are wanted, which provide abstraction from specific hooks.
>
> Who is calling for generic APIs? Application authors are calling for
> an easy to use solution. So in that instance,
> gtk_widget_set_color_managed (widget, FALSE) is easier to use than
> pushing all the rendering out to another library in yet another pixel
> conversion buffer.

The APi is still generic in the way it works for e.g. displaying and 
printing. Thats what I mean with abstracting from (hardware) specific 
hooks.

>> Compiz provides hooks into the GPU during compositing and deploys Oyranos to
>> provide fast desktop colour correction. Or the image_display code in Oyranos
>> uses native CPU conversion through lcms, or an other CMM, to provide a very
>> flexible approach. Yes, I agree, specific hooks are useful and widely
>> deployed. They are on the plan
>> of OpenICC and Oyranos since years.
>
> I think they are on the plan for Oyranos, but they're certainly not on
> the plan for colord and GCM.

As long as your components provide means to opt out of colour management, 
Oyranos or other code can be used for more specialised tasks.

> I'm really not sure if OpenICC == Oyranos these days.

OpenICC is about easy, flexible and portable colour management, with a 
emphasize on Open.


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