1. 17 Oct, 2020 8 commits
  2. 16 Oct, 2020 6 commits
  3. 15 Oct, 2020 3 commits
  4. 13 Oct, 2020 1 commit
  5. 12 Oct, 2020 2 commits
    • Jehan's avatar
      meson, autotools, CI: simplify plug-in binding build options. · e77d9517
      Jehan authored
      For Python, Lua and Javascript, make the option boolean (with 'yes'
      being the default). No need of a warning when not installing the
      plug-ins as this would have been disabled explicitly anyway. When
      installing the plug-ins, only make interpreter checks as precautionnary
      verifications which don't actually change anything (except outputting
      some warnings if interpreters are not found). Basically for these 3
      bindings, the interpreters are only runtime dependencies anyway. So it
      doesn't matter if they are not available at build time. In particular,
      we get rid of the 'force' option.
      
      Vala rules do not change as the vala compiler is indeed needed at build
      time and current checks work correctly. I just add a "Vala plug-ins"
      line in the summary message of the meson configuration, as it was
      missing.
      e77d9517
    • Jordi Mas's avatar
      Update Catalan translation · 47663730
      Jordi Mas authored
      47663730
  6. 11 Oct, 2020 1 commit
  7. 10 Oct, 2020 3 commits
  8. 09 Oct, 2020 8 commits
    • Jehan's avatar
      app: fix wrong extension active state on exit. · 3e0be204
      Jehan authored
      First the deserialize data of extensionrc was wrong. I need to edit the
      pointer to the GList (and dereference it when I need).
      
      Also when inserting an extension into the `running_extensions` hash
      table, I could not reuse the same string as in the `processed` list
      (because this string is going to be freed at end of initialization).
      Just always use the GimpObject name of the extension, since it will stay
      alive for as long as the object is alive.
      3e0be204
    • Jehan's avatar
      app: check extensionrc existence before trying to parse it. · 9c4860b3
      Jehan authored
      On first run, it would not exist (which is normal) which was producing
      an error message on stderr.
      9c4860b3
    • Jehan's avatar
      app: don't show an uninstall button for system extensions. · 91565715
      Jehan authored
      Unlike user extensions, system ones can only be deactivated, not
      uninstalled.
      91565715
    • Jehan's avatar
      plug-ins, extension: goat-exercises becomes a GIMP extension. · ecbc38f9
      Jehan authored
      This is an extension containing a few demo plug-ins. This is good to
      demonstrate the extension format. It will also allow to disable these
      plug-ins (if at some point, one doesn't want to show these demo
      plug-ins anymore).
      
      And finally it deals with the fact that our plug-in code is stupid, as
      it just tries to find the first executable with the same name (minus
      extension) as the plug-in folder. This doesn't go well on Windows, where
      the permission system is non-existent. So our code just ends up trying
      to run the first file with a similar name in a plug-in folder. As the C
      goat-exercise contains both an exe and the C source (and the system
      probably returns files in alphabetic order), GIMP under Windows tries to
      run the C source instead of the executable (this obviously doesn't go
      well).
      We could try to do more complex logics, like not aborting if the first
      file run fails and try the next one in the plug-in folder. Or maybe just
      rename the C file to another name. But any of these is just in the end
      the proof that our plug-in discovery right now is just bogus. The
      extension system is explicit, not based on randomly trying out files.
      Plug-ins entry points are explicitly listed in the metadata manifest.
      ecbc38f9
    • Dušan Kazik's avatar
      Update Slovak translation · 45fb76be
      Dušan Kazik authored
      (cherry picked from commit 1b2f58f8)
      45fb76be
    • Dušan Kazik's avatar
      Update Slovak translation · 14e1d802
      Dušan Kazik authored
      (cherry picked from commit 5551428d)
      14e1d802
    • Dušan Kazik's avatar
      Update Slovak translation · db37b1b1
      Dušan Kazik authored
      (cherry picked from commit 46a12d4a)
      db37b1b1
    • Dušan Kazik's avatar
      Add Slovak translation · f106c231
      Dušan Kazik authored
      (cherry picked from commit 781d5bce)
      f106c231
  9. 08 Oct, 2020 4 commits
  10. 07 Oct, 2020 1 commit
  11. 04 Oct, 2020 2 commits
    • Yuri Chornoivan's avatar
      Update Ukrainian translation · 45ad1c0b
      Yuri Chornoivan authored
      45ad1c0b
    • Jehan's avatar
      plug-ins: change export dialog title when exporting as AVIF. · 5ec3293f
      Jehan authored
      Even though "Export Image as HEIF" is not technically wrong (AVIF is AV1
      encoding inside HEIF container), it is better to be more accurate.
      
      Moreover as Daniel Novomesky was explaining in a MR, nowadays when we
      say "HEIF", we usually mean "HEIC", whereas you'd use the explicit
      "AVIF" naming for HEIF/AV1 images. This seems confirmed by Wikipedia
      which says that HEIC is the "implied default codec for HEIF".
      
      So let's just make the AVIF vs HEIF distinction here (I could have used
      AVIF vs. HEIC which is even more explicit but I decided to keep the
      less-specific yet more used HEIF naming).
      5ec3293f
  12. 03 Oct, 2020 1 commit
    • Jehan's avatar
      gitlab-ci: name the distribution artifacts and small build-deps.sh fix. · 6f4155ee
      Jehan authored
      This should give a nice name to distribution archives so that they are
      not all called `artifacts.zip`. Names will better describe their
      contents (target OS or source and short commit hash, because for CI
      builds, it's important to know which commit is being tested).
      
      Also replace CI_COMMIT_REF_NAME in other artifact names by
      CI_COMMIT_REF_SLUG. Otherwise if a branch has a slash (quite common in
      branch names), only the part after the last slash is used for archive
      naming.
      
      Finally immediately exits from dependency build with error code (!= 0)
      if `crossroad install` command failed.
      6f4155ee