1. 03 Jan, 2019 1 commit
  2. 02 Jan, 2019 5 commits
  3. 29 Dec, 2018 1 commit
  4. 24 Dec, 2018 2 commits
  5. 13 Dec, 2018 3 commits
  6. 12 Dec, 2018 1 commit
  7. 11 Dec, 2018 2 commits
  8. 10 Dec, 2018 1 commit
  9. 07 Dec, 2018 4 commits
  10. 04 Dec, 2018 1 commit
  11. 30 Nov, 2018 3 commits
    • Debarshi Ray's avatar
      gegl, thumbnailer: Don't use gegl:save-pixbuf · 38cea1a9
      Debarshi Ray authored
      ... to convert a GeglBuffer to a GdkPixbuf. This is part of a general
      trend of moving away from using graphs to convert a GeglBuffer to and
      from GdkPixbuf.
      38cea1a9
    • Debarshi Ray's avatar
      gegl: Add photos_gegl_pixbuf_new_from_buffer · 5f54518a
      Debarshi Ray authored
      This is part of a new set of APIs for GeglBuffer that don't require the
      creation of a graph. These will allow decoding and encoding image file
      formats to and from a GeglBuffer through asynchronous and cancellable
      methods with error handling. These will follow GIO idioms and be
      similar to the codec APIs for GdkPixbuf. There will be a compatibility
      layer to convert a GeglBuffer to and from GdkPixbuf for legacy reasons.
      
      These APIs will address the current lack of cancellation and error
      handling in gegl:load, and make it easier to port existing code away
      from GdkPixbuf.
      
      Bump minimum GdkPixbuf version to 2.36.8.
      5f54518a
    • Debarshi Ray's avatar
      7128f1df
  12. 23 Nov, 2018 1 commit
  13. 22 Nov, 2018 3 commits
  14. 18 Nov, 2018 2 commits
  15. 15 Nov, 2018 3 commits
  16. 14 Nov, 2018 2 commits
    • Debarshi Ray's avatar
      build: Add tap-driver.sh and tap-test from GLib · af396b42
      Debarshi Ray authored
      The GLib documentation suggests that tap-driver.sh and tap-test be
      copied into the root directory. It's not clear what difference that
      makes, though.
      
      [1] GLib commit 17e29bebd9a8dc8c
          https://bugzilla.gnome.org/show_bug.cgi?id=788561
      
      !80
      af396b42
    • Debarshi Ray's avatar
      build: Unbreak the environment for the Autotools serial test harness · 7a3135b9
      Debarshi Ray authored
      Autotools' serial test harness uses TESTS_ENVIRONMENT, and doesn't
      support AM_TESTS_ENVIRONMENT [1]. The latest version of glib-tap.mk in
      GLib targets the newer and default parallel test harness, and removing
      the "serial-tests" Automake option breaks the graphical test:
        make[5]: Entering directory
          '/home/rishi/devel/gnome-photos/git/gnome-photos/builddir/tests'
        ERROR: basic.py - missing test plan
        tap-driver.sh: internal error getting exit status
        tap-driver.sh: fatal: I/O or internal error
        make[5]: *** [Makefile:1207: basic.py.log] Error 1
      
      Fortunately, there was no significant breakage because the existing
      test doesn't use APIs like g_test_build_filename, g_test_get_filename,
      and g_test_get_dir, which would have been affected by the missing
      G_TEST_BUILDDIR and G_TEST_SRCDIR environment variables.
      
      Since the Autotools build is deprecated, it's easier to stick to the
      serial harness instead of trying to fix the graphical test to work with
      the parallel setup. Therefore, this partially reverts commit
      0ce96a49 by re-introducing
      TESTS_ENVIRONMENT instead of AM_TESTS_ENVIRONMENT.
      
      [1] https://www.gnu.org/software/automake/manual/html_node/Serial-Test-Harness.html#Serial-Test-Harness
      
      !80
      7a3135b9
  17. 04 Nov, 2018 1 commit
  18. 03 Nov, 2018 1 commit
  19. 02 Nov, 2018 2 commits
  20. 31 Oct, 2018 1 commit
    • Debarshi Ray's avatar
      application, thumbnailer: Remove redundant GResource registration · 8a70b969
      Debarshi Ray authored
      GResources in the form of C source files generated by
      glib-compile-resources(1) without the --manual-register flag, are
      automatically registered as long as the compiler supports constructor
      and destructor functions. Given that there's no explicit desire to
      support compilers without such support, codified by the lack of the
      --manual-register flag, calling g_resources_register is redundant.
      
      Such statically compiled and linked GResources are automatically added
      as GStaticResources to a list internal to GIO by the generated
      constructor function, and are lazily registered whenever their
      contents are referred to by their global path or URI.
      
      This is unlike standalone *.gresource bundles. Those are GVariant
      database (or GVDB) files, which need to be explicitly registered with
      g_resources_register after being loaded with g_resource_load, so that
      their contents can be referred to by their global path or URI.
      
      !77
      8a70b969