2010/1/11 Jon Cruz j...@joncruz.org:
This probably also means that you need to take (at least) Win32 and OS X
into account when designing the public GTK+ APIs - e.g. you need to make
sure the API can be implemented on these platforms preferably using
native Win32 and OS X color management
On Tue, 2010-01-12 at 18:54 +, Richard Hughes wrote:
Everything is converted to sRGB is one possible solution, but
things need to be explicit.
I think shoehorning everything into sRGB would be a very bad idea.
I can see a very good argument for the colour managed GtkImage
converting to
On Jan 7, 2010, at 9:01 AM, David Zeuthen wrote:
This probably also means that you need to take (at least) Win32 and OS X
into account when designing the public GTK+ APIs - e.g. you need to make
sure the API can be implemented on these platforms preferably using
native Win32 and OS X color
On Tue, 2010-01-05 at 13:44 +, Richard Hughes wrote:
Now, Matthias has already said that he's not keen on a lcms dep for
GTK, (which I understand) but would adding the functionality to
GtkImage and registering an extension point be a wise thing to do? In
this case we add a lcms module (or
The observant among you will have noticed the icc-profile GdkPixbuf
option being added to GTK git master recently. This allows us to do
some clever stuff when reading and writing embedded color profiles. At
the moment I'm using this functionality in GcmImage[1] (superclass of
GtkImage) that
