Thanks mental for correcting & completing this spec. About the open points:
- Should surface profile/color rendering changes be allowed once the surface is being actively used?
Why should we allow this ? Is there any use case ? The ones I can see are: render the same surface with two different profiles at the same time (e.g. on a multihead screen with different profiles, but is'nt X already handling that, batch export of the same file in many different colorspaces)
- How should gradients work in this regime?
What is the issue here ? like we have a set_source_icc_color, we can have a set_stop_icc color, isnt'it ?
- How should *cairo_color_profile_t*s be created/loaded?
lcms provides 2 ways, load from a file or from memory. I think cairo should provide the same ways, I dont see an additional one that could bring some benefit here, appart from direct reuse of a lcms handler for applications already using lcms like inkscape but that's not really clean - makes cairo API depend from lcms API.
To get things going on the cairo side, do you think I should notify the cairo ML about this blue print ?
Kind regards, Aubanel.
2008/2/22, Aubanel MONNIER <aubanel@...400...>:
2008/2/22, Alexandre Prokoudine <alexandre.prokoudine@...400...>:
On Fri, Feb 22, 2008 at 9:13 PM, Aubanel MONNIER wrote:
To get the ball rolling, what do you think if I setup a wiki page to
put
together something we could propose to the cairo ML ?
Or you could start a blueprint _and_ a wiki page :)
Done:
https://blueprints.launchpad.net/inkscape/+spec/icc-for-cairo Feel free to alter the wiki if you have some better ideas or spot some misunderstandings/errors on my side.