57ca3f4807
The gimp_procedure_run() already existed, though it was with an ordered GimpValueArray array of arguments. Its usage feels redundant to the series of gimp_pdb_run_procedure*() functions (which is confusing), but gimp_procedure_run() was actually a bit more generic, because it does not necessarily calls GimpProcedure-s through the PDB! For instance, it can runs a local GimpProcedure, such as the case of one procedure which would want to call another procedure in the same plug-in, but without having to go through PDB. Of course, for local code, you may as well run relevant functions directly, yet it makes sense that if one of the redundant-looking function is removed, it should be the more specific one. Also gimp_procedure_run() feels a lot simpler and logical, API wise. A main difference in usage is that now, plug-in developers have to first explicitly look up the GimpPdbProcedure with gimp_pdb_lookup_procedure() when they wish to call PDB procedures on the wire. This was done anyway in the gimp_pdb_run_procedure*() code, now it's explicit (rather than calling by name directly). Concretely: * gimp_pdb_run_procedure(), gimp_pdb_run_procedure_config() and gimp_pdb_run_procedure_valist() are removed. * gimp_procedure_run() API is modified to use a variable args list instead of a GimpValueArray. * gimp_procedure_run_config() and gimp_procedure_run_valist() are added. * gimp_procedure_run_config() in particular will be the one used in bindings which don't have variable args support through a (rename-to gimp_procedure_run) annotation. |
||
|---|---|---|
| .. | ||
| ftx | ||
| tinyscheme | ||
| meson.build | ||
| README | ||
| scheme-marshal-return.c | ||
| scheme-marshal-return.h | ||
| scheme-marshal.c | ||
| scheme-marshal.h | ||
| scheme-wrapper.c | ||
| scheme-wrapper.h | ||
| script-fu-arg.c | ||
| script-fu-arg.h | ||
| script-fu-command.c | ||
| script-fu-command.h | ||
| script-fu-compat.c | ||
| script-fu-compat.h | ||
| script-fu-dialog.c | ||
| script-fu-dialog.h | ||
| script-fu-enums.h | ||
| script-fu-errors.c | ||
| script-fu-errors.h | ||
| script-fu-interface.c | ||
| script-fu-interface.h | ||
| script-fu-intl.h | ||
| script-fu-lib.c | ||
| script-fu-lib.h | ||
| script-fu-proc-factory.c | ||
| script-fu-proc-factory.h | ||
| script-fu-regex.c | ||
| script-fu-regex.h | ||
| script-fu-register.c | ||
| script-fu-register.h | ||
| script-fu-run-func.c | ||
| script-fu-run-func.h | ||
| script-fu-script.c | ||
| script-fu-script.h | ||
| script-fu-scripts.c | ||
| script-fu-scripts.h | ||
| script-fu-types.h | ||
| script-fu-utils.c | ||
| script-fu-utils.h | ||
| script-fu.def | ||
About libscriptfu libscriptfu is part of GIMP. It is not generally useful except by GIMP. The libscriptfu library is used by plugin executables, and the PDB procedures they create, all part of the "ScriptFu" machinery. The libscriptfu library is not intended for third-party developers, only for core GIMP developers. Headers for libscriptfu might not be installed. This directory contains three libraries: libscriptfu, tinyscheme, and ftx. The tinyscheme library contains a TinyScheme interpreter. The ftx library extends the TinyScheme interpreter, adding file functions to the Scheme language. The libscriptfu library contains both the tinyscheme and ftx libraries. The libscriptfu library wraps the TinyScheme interpreter, specializing it for GIMP. The script-fu executable uses the libscriptfu library, to interpret Scheme scripts that GIMP users refer to as "plug-ins." These libraries depend on other libraries, e.g. math, libgimp, glib, etc. Coupling between the executables and the libraries should be in one direction: source for the inner libs should not include headers from the outer executables. This lets you more easily update the inner libraries (which originated elsewhere and might be maintained elsewhere), and change the outer executables (which are subject to change by GIMP developers.) Example (which may change): The script-fu executable is a plugin file that implements PDB procedures: extension-script-fu, script-fu-console, script-fu-text-console, script-fu-eval, and script-fu-server. Each of those PDB procedures runs as a separate process. Each of those processes uses libscriptfu. The main PDB procedure is extension-script-fu, which is a long-lived process. It is a PDB procedure of PDBProcedureType EXTENSION. It interprets the Scheme scripts that user's call "plug-ins." Rarely two of the PDB procedure processes run concurrently. When they do, and libscriptfu is built as a shared library, the read-only, code portion of the library is only loaded in memory once.