On 04/05/2016 02:10 PM, Sven Claussner wrote:

On  4.4.2016 at 3:56 PM Elle Stone wrote:
On 03/27/2016 02:44 PM, C R wrote:
* The ability to edit in RGB working color spaces other than sRGB.

I'm for this, too.
sRGB is from the 1990's and made for the web.
Life goes on. Modern monitors aim to get as much AdobeRGB coverage
as possible and that's not the end yet.
If we aim to provide state-of-the-art technology we should not stick to
sRGB, but be open for flexible solutions.
See https://bugzilla.gnome.org/show_bug.cgi?id=737778 for instance.
As Alex says, it takes just one developer to work on it. I think we
can start with the above mentioned bug report and go on from that.

Some of the specific code-related information in that particular bug report is out of date, not surprising as I posted the bug report in December 2014. The general issues remain. The specific locations of the hard-coded parameters haven't changed too much (GEGL has fewer such locations). But the specific functions that call on the hard-coded parameters have changed a bit.

I started a branch of this current thread to ask some specific questions regarding a couple of babl functions that might be useful for conveying RGB color space information from GIMP to babl, and also about the idea of coding in a selection of well-behaved RGB working spaces: https://mail.gnome.org/archives/gimp-developer-list/2016-April/msg00049.html


gimp-developer-list mailing list
List address:    gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Reply via email to