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

[Richard Hughes]

On 4 February 2011 15:08, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
> That would be really phantastic. Passing through of ICC profiles as meta
> data to backends and so on was discussed in long threads. Would be nice to
> see it actually happen. As well having Gtk and Qt handle ICC profiles during
> loading of images like PNGs would be great as well.

I added the required bits to GDK about one year ago. Now there needs
to be some work done in cairo. Then it becomes easy to fix.

> Its not a good thing. As vendor of a Linux distribution you might argue this
> way. Application developers and even more end users want consitency, not
> have to learn three languages for the same thing. In that sense
> it would be a terrible idea to make cairo behave different on osX, Linux or
> Windows platforms. Btw. thats completly against one major goal of cairo, to
> keep output consitent. So platform abstraction matters.

I'm not saying that at all. I'm talking about the framework. If cairo
wanted to use colorsync on OSX and colord on Linux that's fine for me.

> 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.

> 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. I'm really not sure if OpenICC == Oyranos
these days.

Richard.