[Gegl-developer] Public GEGL API Reference

[Martin Nordholts]

I think gegl_node_disconnect feels more 'safe' than passing NULL to
gegl_node_connect_from, because I think connect_from implies that it
expects something, i.e. that passing it NULL would cause a segfault.

If the method was named gegl_node_set_input, then passing NULL would
feel more 'safe'. I still think connect_from is a better method name
though, hence I think having a gegl_node_disconnect makes sense.

Well, that's all, maybe because I'm semi familiar with the API already.
I think the docs seems to cover the API nicely; more questions will
probably arise when I have time to start using the API more extensively.

- Martin Nordholts





> Work is under way on documenting the GEGL API. The core of the API is
> rather small (less than 15 entry points for the core of creating and
> processing image compositions, and the rest is syntactic sugar or
> state queries).
> 
> Please also look through this API with a critical eye and report thoughts
> on the API back to the mailing list.
> 
> Improvements to the text itself are best sent as a patch against gegl/gegl.h.
> 
> A snapshot of the documentation can be found here:
> http://gegl.org/api.html
> 
> Later this will contain the api reference for the actual release and
> be a part of the GEGL documentation (as it is in SVN now if you run
> autogen.sh / make api.html in docs. After a checkout (assuming you've
> got ruby installed).
> 
> /Øyvind K.
>