161b3c5331
libgimpbase:
- Mew GimpFileChooserAction enum type: basically a near-mapping of
GtkFileChooserAction (GTK is not accessible from libgimpbase) with
an added GIMP_FILE_CHOOSER_ACTION_ANY.
- New GimpParamSpecFile param spec type: based off
GimpParamSpecObject, it has a default value, but also a none_ok and
action argument. This way, we can also know from the argument type
if this is a file argument meant for selecting a normal file or a
folder, or for saving into a file, or for creating a directory.
libgimp, plug-ins:
- All existing file arguments (until now using a standard
GParamSpecObject param with GFile value type) were moved to the new
GimpParamSpecFile.
- Script-Fu in particular will now generate the appropriate param type
depending on whether it is an SF-FILENAME or SF-DIRNAME.
- File arguments are now stored between runs as a URI rather than as a
path. As far as I can tell, a GFile always has a URI, but not always
a path (in particular remote file won't have a path).
|
||
|---|---|---|
| .. | ||
| 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-color.c | ||
| script-fu-color.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-progress.c | ||
| script-fu-progress.h | ||
| script-fu-regex.c | ||
| script-fu-regex.h | ||
| script-fu-register.c | ||
| script-fu-register.h | ||
| script-fu-resource.c | ||
| script-fu-resource.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-version.c | ||
| script-fu-version.h | ||
| script-fu-widgets-custom.c | ||
| script-fu-widgets-custom.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.