1. 01 Oct, 2019 1 commit
  2. 26 Sep, 2019 1 commit
    • Jehan's avatar
      Issue #3990: make the status of the XCF docs a bit clearer (hopefully). · 80e2e0a5
      Jehan authored
      Though it may have started as an unofficial document, it is clearly now
      an official one (which should be obvious since it is in our source
      repository, but apparently some people get misled by the historical
      "Status" text to think this to be somehow unofficial).
      So first of all, change the s/official/unofficial/ mention.
      
      Secondly, add a small paragraph explicitly telling that the document is
      complete (and meant to be), to the best of our knowledge. This document
      is a detailed, full and exhaustive written "specification" of the XCF
      format up to GIMP 2.10.x (even though the normative spec is still the
      code itself). Now we are humans, we may have missed something, and if
      so, this is just to be considered as any other bug, and reported to us
      nicely to be fixed.
      80e2e0a5
  3. 21 Sep, 2019 1 commit
  4. 19 Sep, 2019 1 commit
  5. 14 Sep, 2019 1 commit
  6. 13 Sep, 2019 1 commit
  7. 12 Sep, 2019 1 commit
  8. 11 Sep, 2019 1 commit
  9. 10 Sep, 2019 2 commits
  10. 09 Sep, 2019 2 commits
  11. 05 Sep, 2019 1 commit
  12. 03 Sep, 2019 1 commit
  13. 29 Aug, 2019 1 commit
  14. 19 Aug, 2019 1 commit
    • Michael Natterer's avatar
      Move GimpParamSpecString from libgimp back to app · d62e75a4
      Michael Natterer authored
      It's just too weird to be public. Remove its properties from the wire
      protocol and from pluginrc. Instead, have all GParamSpecs' flags on
      the wire and in pluginrc, so we can use stuff like
      GIMP_PARAM_NO_VALIDATE.
      
      Port the remaining few places to GIMP_PROC_ARG_STRING().
      
      I'm sure something is broken now wrt UTF-8 validation,
      will add tighter checks in the next commit.
      d62e75a4
  15. 18 Aug, 2019 1 commit
  16. 16 Aug, 2019 1 commit
    • Niels De Graef's avatar
      libgimpconfig: Prevent GIR conflicts in GimpConfigWriter · 284ba5c8
      Niels De Graef authored
      GimpConfigWriter contains several constructors with the convention
      `gimp_config_writer_new_* ()`. This will lead to problems however with
      languages like Vala, where it cannot disambiguate the following:
      
      ```
      // calls config_writer_new_string()
      Gimp.ConfigWriter w = new ConfigWriter.string("xxx");
      // calls config_writer_string()
      w.string("xxx")
      ```
      
      Using `from_` in constructors is general practice in GObject-bsed
      libraries because of this.
      
      This also fixes an error when trying to use vapigen on the GIMP .GIR
      file.
      284ba5c8
  17. 15 Aug, 2019 4 commits
  18. 14 Aug, 2019 1 commit
  19. 13 Aug, 2019 1 commit
  20. 11 Aug, 2019 1 commit
  21. 10 Aug, 2019 4 commits
  22. 09 Aug, 2019 3 commits
  23. 05 Aug, 2019 1 commit
    • Niels De Graef's avatar
      docs: Fix warnings for annotations · e77382ee
      Niels De Graef authored
      Right now, we get the following warnings when building the docs:
      
      > gtk-doc.xsl: For acronym (nullable) no value found
      
      This is because we're not adding the generated annotation glossary to
      the docs sgml (presumably because we didn't need it as we didn't use
      GObject-Introspection yet). This commit adds those lines and thus fixes
      the warnings.
      e77382ee
  24. 03 Aug, 2019 1 commit
  25. 01 Aug, 2019 4 commits
  26. 25 Jul, 2019 1 commit
  27. 24 Jul, 2019 1 commit