Re: [Gimp-developer] [Gegl-developer] babl roadmap

On Fri, Oct 17, 2014 at 1:39 PM, Elle Stone
<ellestone ninedegreesbelow com> wrote:
On 10/17/2014 07:08 AM, Øyvind Kolås wrote:

On Fri, Oct 17, 2014 at 1:06 PM, Elle Stone
<ellestone ninedegreesbelow com> wrote:

On 10/17/2014 06:59 AM, Øyvind Kolås wrote:

As a former researcher at a national color science laboratory, and a
major contributor to babl and GEGL; I probably have no idea about
these things – and how the spectral data in named color ICCv4 profiles
might be used.
Nobody doubts your intelligence, acumen, or accomplishments. Not even me.

Then what is the purpose of continuing to endlessly perpetuate this
discussion, asking people to read about spectral color management,
when our roadmaps barely have good colorimetric management in scope?
For the sake of argument alone?

The point of this "endless discussion" is that unbounded sRGB is a
singularly bad way to forcibly recast the user's RGB data for RGB image

The code for converting to unbounded sRGB isn't yet in place.
The babl roadmap lays out a plan to complicate the existing code, apparently
only to turn around and straighten it out again.

What you see as complicating the existing code is normal when one does
something known as refactoring, the roadmap documents the road towards
the goal – and isn't even a complete roadmap since we don't know all
we will know when we are further along on it.

GIMP is not the only project using GEGL; nor is it the only user
interface on top of GEGL. GEGL pipelines need to be able to deal with
arbitrary counts of RGB spaces; which also GIMP need for having
multiple project use open and doing cross project copy-paste, clone
etc. One of the other GEGL UIs is this

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]