1. 30 May, 2017 1 commit
  2. 29 May, 2017 1 commit
  3. 28 May, 2017 5 commits
  4. 27 May, 2017 3 commits
  5. 26 May, 2017 4 commits
  6. 25 May, 2017 2 commits
    • Alexandre Prokoudine's avatar
      Update Russian translation · be513e04
      Alexandre Prokoudine authored
    • Jehan's avatar
      plug-ins: install python-console plug-in in its own subdirectory. · e9851102
      Jehan authored
      As a consequence of commit efae55a7, plug-ins should not install
      data/library files alongside on the root plug-ins/ directory. If they
      have such files, they should create a subdirectory named as the entry
      point file. Obviously we should be the first to follow this guideline.
      We had one such plug-in: python-console.py, which is importing
      pyconsole.py. Let's have both these files under
  7. 24 May, 2017 1 commit
    • Jehan's avatar
      app: allow plugin inside first-level directories of plug-ins folders. · efae55a7
      Jehan authored
      We don't search recursively but only at the first level. If a plugin is
      in its own subdirectory, the entry point has to be named the same (minus
      extension) as the directory. For instance my-plugin/my-plugin for a
      binary, or my-plugin/my-plugin.(py|exe|…).
      This way, a plugin can load shared objects (libraries, other script
      files, etc.) without polluting the main plug-ins directories, and in
      particular without interfering with other plug-ins.
      This is a first step to fix bug 757057 (DLL files which were used in
      various plugins).
  8. 23 May, 2017 4 commits
    • Jehan's avatar
      libgimpbase: minor tab cleaning. · cb023262
      Jehan authored
    • Jehan's avatar
      desktop: add a test for strict validation of appdata file. · 7e25248f
      Jehan authored
      This way we can be warned quickly about any AppStream issue (cf. bug
      782759). This test requires web access for screenshot verification.
      Packagers are invited to use --without-appdata-test option if they want
      to skip the test (for instance if build environment has restricted
      network access).
    • Jehan's avatar
      desktop: use https for everything, even the screenshots. · 7e224888
      Jehan authored
      Even though there is automatic redirection anyway, better to explicitly
      set https. :-)
    • Ell's avatar
      enums: run gimp-mkenums from the build dir · 5bcde32c
      Ell authored
      Commit 1e6acbd4 modified the
      generated enum recipes to run gimp-mkenums from the source
      directory, instead of the build directory, so that only the
      basenames of the corresponding header files would appear in
      the comment at the top of the generated files.  This was a
      mistake -- $(GIMP_MKENUMS) is expecting to be invoked from the
      build directory.
      Switch back to running gimp-mkenums from the build directory.  To
      avoid including the relative path from the build directory to the
      source directory in the generated file, add a @basename@ production
      variable to gimp-mkenums, which exapnds to the basename of the
      input file, and use it instead of @filename@ in the recipes for the
      generated enum files.
  9. 22 May, 2017 5 commits
  10. 21 May, 2017 4 commits
    • Jordi Mas's avatar
      Update Catalan translation · 293aecf9
      Jordi Mas authored
    • Piotr Drąg's avatar
      Update Polish translation · cb5d9770
      Piotr Drąg authored
    • Ell's avatar
      app: future-proof XCF layer blend/composite props · e7d781ff
      Ell authored
      The layer blend space, composite space, and composite mode
      properties have a special AUTO value, which may map to different
      concrete values based on the layer mode.  Make sure we can change
      this mapping in the future, without affecting existing XCFs (saved
      after this commit), by encoding these properties as follows:
      When saving an XCF, if the property has a concrete (non-AUTO)
      value, which is always positive, encode it as is.  If the property
      is AUTO, which is always 0, encode it as the negative of the value
      it actually maps to at the time of saving (note that in some cases
      AUTO may map to AUTO, in which case it's encoded as 0).
      When loading an XCF, if the encoded property (stored in the file)
      is nonnegative, use it as is.  Otherwise, compare the negative of
      the encoded property to the value AUTO maps to at the time of
      loading.  If the values are equal, set the property to AUTO;
      otherwise, use the concrete value (i.e., the negative of the value
      stored in the XCF).
      Note that XCFs saved prior to this commit still load fine, it's
      simply that if we change the AUTO mapping in the future, all their
      AUTO properties will keep being loaded as AUTO, even if the
      resulting concrete values will have changed.
    • Marco Ciampa's avatar
      Updated Italian translation · 7f7d8b43
      Marco Ciampa authored
  11. 19 May, 2017 10 commits