On 11/05/2014 07:34 AM, Alexandre Prokoudine wrote:
On Tue, Nov 4, 2014 at 10:27 PM, Elle Stone wrote:
Another advantage to forking babl and GEGL for GIMP is that GIMP's fork of
babl and GEGL could be GPLed, thus freeing the GIMP devs to add FFTW
(Fourier transforms, http://www.fftw.org/) and o
On Wed, Nov 5, 2014 at 4:57 PM, Elle Stone wrote:
> Drop the incredibly paternalistic attitude that the devs know better than
> the GIMP users what GIMP users really need.
Out of curiosity: if we had that attitude, what was the point of
working with a user experience architect from 2006 to 2013,
My apologies in advance for sounding preachy, but here goes:
GIMP developers need to start paying attention to what potential and
actual GIMP users really want and need from their RGB image editor.
I respectfully suggest the following:
Drop the incredibly paternalistic attitude that the devs
On Tue, Nov 4, 2014 at 10:27 PM, Elle Stone wrote:
> Another advantage to forking babl and GEGL for GIMP is that GIMP's fork of
> babl and GEGL could be GPLed, thus freeing the GIMP devs to add FFTW
> (Fourier transforms, http://www.fftw.org/) and other new functionality to
> GIMP. FFTW is GPLed.
Hi,
On Tue, Nov 4, 2014 at 7:27 PM, Elle Stone
wrote:
[...]
Skipping all the main contents, since I don't know enough to be able
to tell what is "the right thing to do" or not.
Just a comment on the license and forking part.
> Another advantage to forking babl and GEGL for GIMP is that GIMP's f
Below explains why GIMP should fork babl and GEGL for use just with GIMP:
Hacker News picked up an article from my website: The Sad State of High
Bit Depth GIMP Color Management
(http://ninedegreesbelow.com/photography/sad-state-of-high-bit-depth-gimp-color-management.html)
In the Hacker News
