RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

API renaming due to merging of GeglGraph and GeglNode

This discussion is connected to the gegl-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.
API renaming due to merging of GeglGraph and GeglNode Øyvind Kolås 04 Jan 23:33
API renaming due to merging of GeglGraph and GeglNode Martin Nordholts 05 Jan 08:14
Øyvind Kolås
2007-01-04 23:33:02 UTC (over 17 years ago)

API renaming due to merging of GeglGraph and GeglNode

I am doing some serious API renaming in GEGL due to merging of GeglGraph and GeglNode classes. The reason I'm doing the merging is that it seems to make it
cleaner when writing a ruby binding, and that part of the code has some issues with
using inheritance without transmogrification.

The global replacements I've done are:

s/gegl_graph_/gegl_node_/ s/gegl_node_new_node/gegl_node_new_child/ s/gegl_node_create_node/gegl_node_create_child/ s/gegl_node_input/gegl_node_get_input_proxy/ s/gegl_node_output/gegl_node_get_output_proxy/

Any comments? My plan is to push out 0.0.6 which will contain touch ups of the API
as well as the build changes that have already gone into the tree this weekend.

(PS: for a more up to date with svn version of the GEGL documentation see http://pippin.gimp.org/gegl/ , the version at http://gegl.org/ will probably in the future document the last tarball release.)

/Øyvind K.

Martin Nordholts
2007-01-05 08:14:23 UTC (over 17 years ago)

API renaming due to merging of GeglGraph and GeglNode

Comment:
I think all those renames are good.

- Martin N.

tor 2007-01-04 klockan 23:33 +0100 skrev Øyvind Kolås:

I am doing some serious API renaming in GEGL due to merging of GeglGraph and GeglNode classes. The reason I'm doing the merging is that it seems to make it
cleaner when writing a ruby binding, and that part of the code has some issues with
using inheritance without transmogrification.

The global replacements I've done are:

s/gegl_graph_/gegl_node_/ s/gegl_node_new_node/gegl_node_new_child/ s/gegl_node_create_node/gegl_node_create_child/ s/gegl_node_input/gegl_node_get_input_proxy/ s/gegl_node_output/gegl_node_get_output_proxy/

Any comments? My plan is to push out 0.0.6 which will contain touch ups of the API
as well as the build changes that have already gone into the tree this weekend.

(PS: for a more up to date with svn version of the GEGL documentation see http://pippin.gimp.org/gegl/ , the version at http://gegl.org/ will probably in the future document the last tarball release.)

/Øyvind K.