My planned approach was to make colord and Oyranos plugins for Weston. The plugins would provide the CMSes with information about the outputs and Weston in return gets ICC profiles for them (which contains gamma curves). Weston needs the full ICC profile in order to do proper color correction and the CMSes needs information about the outputs, so everyone's happy.
On Tue, Apr 2, 2013 at 11:24 AM, Richard Hughes <[email protected]> wrote: > On 2 April 2013 06:45, Graeme Gill <[email protected]> wrote: >> The display's ICC profile will also be stored in the _ICC_PROFILE atom, >> to make it available to the display client, so that color can be adjusted >> appropriately for that display. Using XRandR it will/should >> also be set in an output property. > > There's not going to be _ICC_PROFILE atoms in weston, nor XRandR > output properties, so clients will need to query the CMM directly > (which is a good thing IMO). The grand idea is to use a sub-surface > with a tagged color profile, which means applications don't have to > care about CM unless they want to opt out a region and handle > everything themselves. > > Richard > _______________________________________________ > wayland-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/wayland-devel _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
