On Wed, Aug 20, 2008 at 5:30 AM, John Culleton <[EMAIL PROTECTED]> wrote:
> On Tuesday 19 August 2008 10:03:52 am Michael Schumacher wrote:
>> > Von: "David Gowers" <[EMAIL PROTECTED]>
>> >
>> > > On Monday 18 August 2008 02:35:51 am you wrote:
>> Where does the "you" come from?
>> > >> You will notice that there's a --disable-docs option. Have you
>> > >> tried to use that?
>> There have been segfaults when GEGL was used to process the demo
>> images in the docs directory, and thus...
>> > > OK I did that and after updating a bunch of libraries Gimp
>> > > 2.5.2 compiles and starts.  But when I open the default
>> > > document it shows up black.
>> ... it should IMO first be verified that GEGL does work at all,
>> e.g. by running the gegl executable and checking what does happen
>> then.
>> HTH,
>> Michael
> Well I have deinstalled 2.5.2 and gone back to 2.4.5. I hope the value
> added by the gegl package is worth the extra install effort and the
> greater risk for failure.
On every one of the 5 installations I've done, it's been easy to do
and worked fine immediately. You simply lucked out. That said, GEGL
isn't production standard yet -- mainly because it needs more testing
(which GIMP will provide by using it). So, your efforts to get it
working on your system are appreciated.

GEGL is a huge step for GIMP towards doing image processing in the
'right way' -- ie. flexible, avoiding unnecessary destruction of
useful data, and easy to extend. One of the concrete benefits of GEGL
is, it allows GIMP to replace special casing for RGB, Gray, Indexed
image types with code that can simply work without special casing --
less code == less bugs.

Another is that it reduces the size of the GIMP core codebase (which
is sorely needed, esp. for attracting new developers) by allowing any
special-case optimizations that are wanted to be done outside GIMP and
plugged into GEGL. (it is currently a bit slow, so there will need to
be optimizations)

I hope you will try again, perhaps when 2.6 is released.

Gimp-user mailing list

Reply via email to