Re: [Gegl-developer] Terminology, Summary

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

 



I think this summarises most of the discussion.

This list should simplify communication with gimp, other projects and
people in general when discussing how to utilize gegl's compositing model.

---------------------------------------------------------------------------
connection
    The link defining image flow in a graph, going from an output pad in 
    one node to a input pad in another node.
graph
    A directed acyclic graph, consisting of nodes. The graph has an inter-
    face in common with nodes, allowing sub-graphs.
node
    An element within a graph. that either creates, processes or consumes
    data passed in the graph.

    composer node
        A type of Node that has more than one input pad, compositing
        operations, integration of an alpha mask, merging of R,G and B 
        into a color image and other operations.
    decomposer node
        A type of node that has more than one output pad.
    filter node
        A node that has exactly one input pad and one output pad, for
        instance color correction, blur, affine transformation.
    source node
        A node that has output pad(s) but no input pads, examples are 
        file loaders, frame grabbers, blank images, solid noise generators 
        and in-memory buffers.
    sink node
        A node that has input pad(s) but no output pads, examples are file
        writers, display, in-memory buffer (for instance,. thumbnails, and
        customized display widgets)

pad
    The part of a node that exchanges image content, input pads consume 
    image data, whilst output pads are places where image data can be 
    requested.  Multiple connections are allowed from an output pad, whilst 
    only one connection can exist to an input pad.
property
    Properties are what control the behavior of nodes, properties are named,
    have defined types and ranges, and probably provide hints about their
    usage. e.g. a string can be (amongst other things) a file parameter or
    font defintion, both should be handled differenlty in an autogenerated
    UI.).
---------------------------------------------------------------------------

More terms might be added, but this should be enough to describe most of the
fundamental framework, and illustration in ascii follows:

    .-----------.
    |           |<------- source node
    |load_image |
    |   ,---.<----------- output pad
    `---' | `---'
       .--^--.
      /       \<--------- connection
     |   .---. | .---.
     |   |   `---'<------ input pad
     |   |coloradj   |
     |   |   .---.   |<-- filter node
     |   `---'/  `---'
     |       /
     |      /
 .-. | .-. / .-.
 | `---' `---' |<-------- composer node
 | sidebyside  |
 |    .---.    |
 `----' | `----'
        |
  .---. | .---.
  |   `---'   |<--------- sink node
  |display    |
  |           |
  `-----------'

/Øyvind K.


-- 
  .^.
  /V\    Øyvind Kolås,  Gjøvik University College, Norway 
 /(_)\   <oeyvindk@xxxxxx>,<pippin@xxxxxxxxxxxxxxxxxxxxx>
  ^ ^    

[Index of Archives]     [Yosemite News]     [Yosemite Photos]     [gtk]     [GIMP Users]     [KDE]     [Gimp's Home]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux