I have posted a "Make shortcut" plugin to the Gimp Registry.  It lets a
user choose from a view of the menu tree of plugins, to create a new
plugin (a script) that is a shortcut to a target plugin.

It is very rudimentary, but could be extended into a visual editor of
sorts, to create named sequences of actions.

The visual editor (proposed here as a GSOC project:
http://archives.free.net.ph/message/20100325.130320.3246ef1c.en.html )

seems too ambitious.  Sequences are enough, represented by lines of text
for menu items.  Graphical pictures of flowcharts is not necessary, at
least as a start.  (A UNIX perspective: text is enough.)

One problem is that the PDB does not give access to default parameters
of plugins.  It seems that defaults are maintained by the individual
plugins, not by the PDB.  I am not sure there is even a convention for
storing default parameters.  I saw one C-language plugin that stored
default in the data attribute of PDB procedures.  Pygimp plugins seem to
store defaults using Python shelf.  I haven't explored how Scheme
scripts store defaults.  A user of a visual editor would want the

Another problem is that other menu items in GIMP (not plugins) are not
exposed by the PDB.  I have just started to explore, but it seems the
actions (sequences) of other menu items in Gimp might be exposed in the
XML for the other menus of Gimp.  It would be much easier to create a
visual editor if there was a uniform API for determining the actions of
all Gimp menu items (not just the plugins.)

I am not familiar with the "action framework".  I would appreciate a

As to the implementation language, Python seems OK: plenty of support,
portable, high level, objects.

Gimp-developer mailing list

Reply via email to