From: Sven N. <neu...@un...> - 2000-05-04 09:07:32
|
Hi, > > Yes, yes and yes again. But because we don't have any CM support so far > I thoght that it's better to have a plugin that does some sort of > color correction then to keep on hoping that somebody would come up > with an overall strategy for CM. as I said, it is always a good thing to have some working code. We'll want to include some sort of color management with Gimp-2.0. > Can you elaborate a little more about the cdisplay modules? This is the > first time I'm hearing about these modules. Where can I find more > information? Read the code. I'm sorry, but AFAIK that's the only source of information so far. There are two modules implemented in the current developers version (CVS or 1.1.21). Have a look at modules/cdisplay_gamma.c modules/cdisplay_highcontrast.c > There is one aspect of the output transformation for which it makes sense > to do it in a plugin: If you want to do soft proofing with a gamut check > then you have to display the result on the screen. This does not make sense > to do in the print module. One possibility is that the a soft proofing > plugin could query the print plugin about the profile to use and then > work independently from the print module, or we could have some global > settings for color management that the Gimp application owns, but all the > other parts (input, output, soft proofing, ...) would just use this > configuration information to find out which profiles to use, or ... You could store that information using parasites. That would easily allow to have different plug-ins share the same profile data. > There are so many ways of doing this kind of work that it's probably not > up to me to decide which one to take. What I wanted to do is just put > something out that could be used as a basis for further experiments, but > still is useful for doing some real work. It wasn't my intention to discourage you. It's nice to see that someone starts to take color managment for GIMP serious. Salut, Sven |