Am Freitag, 9. Dezember 2016, 12:02:07 CET schrieb Carsten Haitzler: > On Thu, 8 Dec 2016 17:32:37 +1100 Graeme Gill <grae...@argyllcms.com> said: > > Carsten Haitzler (The Rasterman) wrote: > > > i'm curious... is the intent to make it requird that all compositors > > > support color management (and thus have to support all the possible > > > colorspaces> > > > defined)... or are we going to go the path of: > > I'd be happy if there was support for core color management (i.e. > > application color management), before adding layers that depend on the > > core. > > but is the intent that compositors MUST support color management and > applications will fail entirely or fail to display even partly correctly if > compositor doesnt support color management or doesnt support the color > profile/space requested by the client? or will it be expected that apps need > to always be able to convert to sRGB for compatibility and then have added > colorspace capabilities if it's supported? what is the intent?
We can't make support for this protocol mandatory because color correction might be too much overhead for compositors for embedded devices. But I would say that every compositor that does some sort of color correction should also implement the color management protocol. If the protocol is not supported by the compositor you would assume that you have to output the colors in the device color space (or just ignore it if you do not care about accurate colors). _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
