gimp/devel-docs/libgimpbase
Jehan 70a9576f27 app, devel-docs, libgimpbase: s/gimp_parasite_name/gimp_parasite_get_name/…
… 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
2021-04-05 18:36:44 +02:00
..
.gitignore devel-docs: add the newly generated module.actions files to .gitignore 2020-10-25 19:57:30 +01:00
Makefile.am devel-docs: REVERT THIS once module.actions get removed automatically 2020-10-25 20:18:52 +01:00
libgimpbase3-docs.sgml [devel-docs] move version file to deduplicate code 2019-09-09 18:15:13 +00:00
libgimpbase3-overrides.txt devel-docs: change the libgimpbase docs to "libgimpbase3" 2019-07-23 13:47:51 +02:00
libgimpbase3-sections.txt app, devel-docs, libgimpbase: s/gimp_parasite_name/gimp_parasite_get_name/… 2021-04-05 18:36:44 +02:00
libgimpbase3.types Remove GimpInt16Array 2021-02-18 11:32:45 +00:00
meson.build Meson port. 2019-09-11 16:42:04 +02:00