Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-07 Thread Simos Xenitellis
On Thu, Nov 6, 2014 at 10:00 PM, Elle Stone ellest...@ninedegreesbelow.com wrote: On 11/06/2014 12:35 PM, Gary Aitken wrote: Maybe I'm misunderstanding the discussion. Gimp asks when one opens an image what one wants as the working colorspace. But we're talking about operations *after* the

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-07 Thread Elle Stone
On 11/07/2014 04:25 AM, Simos Xenitellis wrote: Hi All, I am a recent subscriber to the list and I have read with interest the recent threads and I am trying to figure out the what next?. Developer resources in any project are generally very limited, so it's important to get more people

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-06 Thread Elle Stone
On 11/05/2014 09:40 AM, Jon Nordby wrote: On 5 November 2014 14:50, Elle Stone wrote: For the babl code that converts an sRGB image to grayscale for use as a layer mask, do you plan to add a new set of functions that convert from UserRGB to grayscale? That code would, of

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-06 Thread Gary Aitken
I'd like to add my penny's worth on this discussion. My primary use of gimp involves editing photographic images, for both web and print purposes. On 11/06/14 05:04, Elle Stone wrote: Speaking as a developer (you all keep telling me I'm a developer), a crucially important guiding principle

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-06 Thread Alexandre Prokoudine
On Thu, Nov 6, 2014 at 8:24 PM, Gary Aitken wrote: If you *ask* the user whether they want to have their data treated as bonified same as GIMP's sRGB and then use optimized sRGB-only code, that's one thing. Doing so behind the user's back, without their consent, that's another thing. That is

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-06 Thread Gary Aitken
Hi Alex, If you *ask* the user whether they want to have their data treated as bonified same as GIMP's sRGB and then use optimized sRGB-only code, that's one thing. Doing so behind the user's back, without their consent, that's another thing. That is disrespecting the user's control over

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-06 Thread Elle Stone
On 11/06/2014 12:35 PM, Gary Aitken wrote: Maybe I'm misunderstanding the discussion. Gimp asks when one opens an image what one wants as the working colorspace. But we're talking about operations *after* the image has been opened and the working colorspace has been established. Once I

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-05 Thread Elle Stone
On 11/04/2014 02:31 PM, Jon Nordby wrote: (apologies for top-posting) Hi Elle, The BABL roadmap[1], which was written in response to comments raised by you (and others), details a mechanism for working with multiple RGB color spaces. It will be possible to create a babl format specifier which

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-05 Thread Elle Stone
In his last post on the topic Pippin said: Once we have the vocabulary to also describe this aspect of the pixelformats used by operations, the first thing we should do is to annotate all the operations which are broken when done with sRGB primaries, then we will be able to continue

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-05 Thread Elle Stone
On 11/05/2014 08:22 AM, Jon Nordby wrote: What you just described IS side-by-side implementations of operations. In an ICC profile color-managed application, sRGB is just another RGB working space. You don't need to special-case sRGB. No it is not. There will be one implementation

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-05 Thread Simon Budig
Elle Stone (ellest...@ninedegreesbelow.com) wrote: Why would any sane developer want to write all the new code and have it exist side by side with equivalent hard-coded sRGB functions? Why would any sane developer want to fork an existing libary and have it exist side by side with an equivalent

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-05 Thread Elle Stone
On 11/05/2014 09:07 AM, Simon Budig wrote: Elle Stone (ellest...@ninedegreesbelow.com) wrote: Why would any sane developer want to write all the new code and have it exist side by side with equivalent hard-coded sRGB functions? Why would any sane developer want to fork an existing libary and

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-05 Thread Jon Nordby
On 5 November 2014 14:50, Elle Stone ellest...@ninedegreesbelow.com wrote: On 11/05/2014 08:22 AM, Jon Nordby wrote: What you just described IS side-by-side implementations of operations. In an ICC profile color-managed application, sRGB is just another RGB working space. You

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-05 Thread Jon Nordby
On 5 November 2014 13:50, Elle Stone ellest...@ninedegreesbelow.com wrote: On 11/04/2014 02:31 PM, Jon Nordby wrote: (apologies for top-posting) Hi Elle, The BABL roadmap[1], which was written in response to comments raised by you (and others), details a mechanism for working with

Re: [Gimp-user] [Gimp-developer] GIMP should fork babl and GEGL

2014-11-04 Thread Jon Nordby
(apologies for top-posting) Hi Elle, The BABL roadmap[1], which was written in response to comments raised by you (and others), details a mechanism for working with multiple RGB color spaces. It will be possible to create a babl format specifier which means