70a9576f27
… and s/gimp_parasite_flags/gimp_parasite_get_flags/ It is better to have a consistent API and the fact is that most getter/setter functions use the _get|set_ naming, but these didn't. I wondered if this was such a great idea to rename these anyway because even though we are breaking API in GIMP 3, is it the best idea to rename when no functional change happened? After discussing with Wormnest, we still agreed it was still better to go for consistency rather than regret later (and be stuck with these names for many more years). Also this fixes these warnings: > [649/1205] Generating gimp-3.0.vapi with a custom command > Gimp-3.0.gir:24162.7-24162.56: warning: Field `Gimp.Parasite.flags' conflicts with method of the same name > Gimp-3.0.gir:24318.7-24318.52: warning: Field `Gimp.Parasite.name' conflicts with method of the same name |
||
|---|---|---|
| .. | ||
| app | ||
| g-ir-docs | ||
| GIMP3-plug-in-porting-guide | ||
| 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