On Mon, Sep 20, 2010 at 2:10 PM,  <oli...@first.in-berlin.de> wrote:
>> Oliver -
>>
>> this rant has no reason to be.  Sorry for that.
>> It makes no sense to start working in a project the size of GIMP
>> without having to learn the code already in there first.
> [...]
>
> I didn't say people should not look into the code.
>
> I meant: before looking into the code, an OVERVIEW on the code base
> would be helpful.
>
> Looking into the code without an overview yields to people with
> too narrow view on the code. Maybe that is good for other people,
> but not for me.

I'll bite ツ

There is various libraries that GIMP depends on:

glib - does portable reusable low level data structures, and includes
GObject which provides the basis for OOP in GIMP
gtk+ - is a UI toolkit that was created for use with GIMP that is now
widely used also elsewhere
babl - is a pixelformat conversion library that provides dynamic and
efficient conversion of pixel formats.
GEGL - is a graph based image processing framework that together with
its plug-ins is destined to replace almost all code in GIMP and its
plug-ins, doing work on the legacy 8bit code in GIMP will most often
result in the brave new world promised by GEGL to be further
postponed.

I maintain two of these projects, babl and GEGL, the following links
point to overviews of the directory structures used for their source
codes:

http://gegl.org/#_directory_overview , http://gegl.org/babl/#DirectoryOverview

/Øyvind K.
-- 
«The future is already here. It's just not very evenly distributed»
                                                 -- William Gibson
http://pippin.gimp.org/                            http://ffii.org/
_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Reply via email to