43d0f0fbd2
Plug-ins that work from different bindings probably want to use their
own list-type to specify arguments, rather than working with a more
cumbersome `GimpValueArray`.
This new API should make it less verbose. For example:
```
args = Gimp.ValueArray.new(5)
args.insert(0, GObject.Value(Gimp.RunMode, Gimp.RunMode.NONINTERACTIVE))
args.insert(1, GObject.Value(Gimp.Image, image))
args.insert(2, GObject.Value(Gimp.Drawable, mask))
args.insert(3, GObject.Value(GObject.TYPE_INT, int(time.time())))
args.insert(4, GObject.Value(GObject.TYPE_DOUBLE, turbulence))
Gimp.get_pdb().run_procedure('plug-in-plasma', args)
```
becomes
```
Gimp.get_pdb().run_procedure('plug-in-plasma', [
GObject.Value(Gimp.RunMode, Gimp.RunMode.NONINTERACTIVE),
GObject.Value(Gimp.Image, image),
GObject.Value(Gimp.Drawable, mask),
GObject.Value(GObject.TYPE_INT, int(time.time())),
GObject.Value(GObject.TYPE_DOUBLE, turbulence),
])
```
|
||
|---|---|---|
| .. | ||
| app | ||
| libgimp | ||
| libgimpbase | ||
| libgimpcolor | ||
| libgimpconfig | ||
| libgimpmath | ||
| libgimpmodule | ||
| libgimpthumb | ||
| libgimpwidgets | ||
| performance-logs | ||
| tools | ||
| .gitignore | ||
| c.vim | ||
| commit-rules.txt | ||
| compositing.txt | ||
| contexts.txt | ||
| debug-plug-ins.txt | ||
| debugging-tips.txt | ||
| exif-handling.txt | ||
| gbr.txt | ||
| ggr.txt | ||
| gih.txt | ||
| gimp-module-dependencies.svg | ||
| GIMP3-API-Changes.txt | ||
| gitlab-milestones.txt | ||
| gpb.txt | ||
| gtkbuilder-porting-guide.txt | ||
| icons.txt | ||
| includes.txt | ||
| Jenkins-Tutorial.odt | ||
| libtool-instructions.txt | ||
| Makefile.am | ||
| meson.build | ||
| os-support.txt | ||
| parasites.txt | ||
| pat.txt | ||
| README | ||
| README.gtkdoc | ||
| release-howto.txt | ||
| release-stats.sh | ||
| structure.xml | ||
| submitting-patches.txt | ||
| tagging.txt | ||
| ui-framework.txt | ||
| undo.txt | ||
| vbr.txt | ||
| version.in | ||
| xcf.txt | ||
Developers documentation
------------------------
This directory holds information that you will find useful if you
develop a GIMP plug-in or want to work on the GIMP core.
See https://wiki.gimp.org/index.php/Main_Page for more information.
app - setup for documentation of the GIMP core;
not built by default since it is huge and
only relevant for core developers
libgimp
libgimpbase
libgimpcolor
libgimpconfig
libgimpmath
libgimpmodule
libgimpthumb
libgimpwidgets - complete libgimp documentation generated from
the source; see README.gtkdoc
tools - the source code for tools used to generate
documentation
gitlab-milestones.txt - describes how the GIMP project uses
milestones in the GNOME gitlab issue tracker
commit-rules.txt - describes rules and things to think
about when creating GIMP commits
contexts.txt - describes how GimpContexts are used in GIMP
debug-plug-ins.txt - how to debug GIMP plug-ins
exif-handling.txt - how GIMP should handle EXIF data
includes.txt - the policy for inclusion of header files
parasites.txt - descriptions of known parasites
release-howto.txt - a check-list for doing a GIMP release
submitting-patches.txt - how to submit a patch for GIMP
tagging.txt - how resource tagging in Gimp works
ui-framework.txt - describes how the GIMP UI framework functions and
how it is implemented
undo.txt - description of the undo system
structure.xml - a DocBook article that gives an overview on
the directory structure of the GIMP source tree,
also check out gimp-module-dependencies.svg
gbr.txt - description of the GBR format used to store
pixmap brushes
ggr.txt - description of the GGR format used to store
GIMP gradients
gih.txt - description of the GIH format used to store a
series of pixmap brushes
gpb.txt - OBSOLETE: description of the GPB format for
pixmap brushes
pat.txt - description of the PAT format for patterns
vbr.txt - description of VBR format used for
"generated" brushes
xcf.txt - description of Gimp's XCF format