I have been trying to teach myself how to write Gimp scripts/plug-ins using Python-Fu (and trying to learn some python along the way, as well).

I have been using the GIMP Python Documentation and a few online tutorials that I have found - Extending Gimp with Python (which is listed on Gimp Chat's GIMP Script Writing Resources thread), Use Python to write plug-ins for GIMP, and Gimp plugins with Python-fu.

According to the GIMP Python Documentation:

The above linked tutorials are consistent with the above.

However, when I was trying to solve an issue that I was having with registering a python plug-in (see my post Python Scripts not Registering in Gimp 2.8), I came across the following posts on other support sites that referenced a plug-in's menu path in the register call differently from the way it was done in the GIMP Python Documentation or the above linked tutorials:

Duplicating a layer (Python plug-in) on Gimp Forums
Attempting to Write Python Plugin and Failing Miserably on Gimp Forums
Gimp: why can't I register this? on stackoverflow

These links indicate that the menu path and the menu name should be separated, with the menu path being the last parameter listed for "register." The stackoverflow link says:



Apparently, either was must work since my python plug-ins based on the materials I first linked seem to work.

My question is: Is there updated documentation on this and other aspects of python-fu? If so, where can I find that documentation? I was thinking that maybe that documentation would have other info that might be helpful.

Thanks in advance for any help.

I can't say I know of any more recent documentation.

"Deprecated" just means the GIMP developers want you to use the new method, because they will eventually stop the old method from working, but it's OK to use it now.

I'll guess the reasoning behind separating the menu label from the menu path is down to language translation, which neatly leads into your question on the GIMP registry site: http://registry.gimp.org/node/27652

The leading underscores are there to mark strings that are suitable for language translation, see Esper's thread about translating to German: viewtopic.php?f=9&t=5648

Kevin

Thanks! What significance do the parentheses surrounding "Input Directory" have:


Thanks for your patience with this noob! :-)

The quotes around "Input Directory" makes it a single entity, not either Input or Directory.

What about the parentheses (brackets) in ---> ("Input Directory") ?

Think of the brackets as a box, in the box you have two items, Input and Directory. If you don't have parentheses a selector will not see them as an entity, it will see them separately.

Thank you!