<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" content="1" /><style type="text/css"> p, li { white-space: pre-wrap; } </style></head><body style=" font-family:'DejaVu Sans'; font-size:12pt; font-weight:400; font-style:normal;"> On Wednesday, May 04, 2011 10:18:57 AM Kai-Uwe Behrmann wrote: > Am 04.05.11, 10:46 -0600 schrieb Chris Murphy: > > On May 3, 2011, at 9:55 AM, Hal V. Engel wrote: > >> This has been brought up on the XOrg email list by members of this list > >> many times in the past. It is always quickly and decisively rejected > >> by those who control the direction of XOrg. Until the XOrg movers and > >> shakers are willing to at least consider the idea nothing will happen > >> with this idea. > > > > Is this something the desktop environment could implement? Is there a way > > for the various desktop environments to agree on a handful of APIs to > > allow for a passthrough (for display and print)? > > The net-color spec is used by the CompICC colour server and some > applications: > http://www.freedesktop.org/wiki/OpenIcc#net-colorspec > Specifying a window region without any ICC profile attached means opt-out. > > > kind regards > Kai-Uwe Behrmann To add some detail. In the past when it was proposed that XOrg should implement CM in it's core the XOrg devs basically said "no this belongs in the composite engine not in XOrg" and "we don't think the GPU has enough horse power to handle this so we are not interested in moving forward with it even if it did belong in XOrg core". At that tiem a little testing by some of our members decisively proved that even a low end GPU can in fact handle this so we know that this was not an issue. But the concern about how this should be architected remained. Does it belong in XOrg core or in the composite engine? Because there was no reason to expect that this would end up in XOrg's core anytime in the foreseeable future, if ever, we mentored a GSoC project to see if doing this in the composite engine via a plugin was possible. This resulted in a compitz plugin that worked under some circumstances but that needed additional work. But it did a convincing job of proving that it was possible. Kia-Uwe has done additional work to the plugin and this now appears to be working nicely. In addition to the plugin Kia-Uwe has written the net color spec that documents how apps can opt-out when needed (IE. to let the app color manage a specific piece of screen real estate). So pass though to the screen is currently fairly well defined and there are even example apps that use this API. See Kia-Uwe's comments above. We currently do not have anything in place for printing pass through. But I think this is one of the things that needs to be considered for the GSoC CPD project and I think it is worth while to put some effort into helping get the requirements/architecture/design in place for the student working on this before the project kick off date (late May). Perhaps by the end of summer we can have both the screen and printing pass through stuff in place in at least in prototypical form. Hal </body></html>