362fae9147
We now save and load layer and channel item sets. Only missing set types are path ones, but the whole path item is just its own exception in the XCF format, and adding support for it, while keeping compatibility with older XCF seem like a small headache. I could do it, but I actually wonder if it is worth it. Would people really need to store sets of paths? Also this commit finally gets rid of any remnant of the old item "link" concept (I think), so we are getting close to merging the branch. |
||
|---|---|---|
| .. | ||
| 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 | ||
| gitlab-mr.md | ||
| gpb.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