What does one node being a child of another do? Why wouldn't you just create all your nodes at top level and connect them? Can you only connect siblings? Does a top level node have an operation?
gegl_node_connect_from and gegl_node_connect_to seem to work opposite from what I'd expect.
Having two operations that do the same thing but with different argument order is usually bad. If they aren't unambiguously named it certainly isn't going to improve readability, which seems to be the intention.
From what I understand one output can be connected to several input. Can one input also read from several outputs, or does a connect_to to an occupied input disconnect the previously connected output? If so, is there any way for a node take an arbitrary number of inputs?
gogl_node_detect seems to have somewhat limited use... I see how it would work for a simple concatenation of images or non-transparent overlays, but what should it return if several inputs are merged?
What are proxies used for? "Route between nodes of a subgraph contained within a node"? Isn't that what normal connections do?
- Håkon
On 1/25/07, Øyvind Kolås <pippin@xxxxxxxx> wrote:
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.
--
«The future is already here. It's just not very evenly distributed»
-- William Gibson
http://pippin.gimp.org/ http://ffii.org/
_______________________________________________
Gegl-developer mailing list
Gegl-developer@xxxxxxxxxxxxxxxxxxxxxx
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer
_______________________________________________ Gegl-developer mailing list Gegl-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer
