1. 20 Apr, 2012 1 commit
    • Alexander Larsson's avatar
      Add GDBusDAaemon, an implementation of a message bus · 9490d67f
      Alexander Larsson authored
      This is mostly complete, sans support for activation. However, its
      not as picky as the libdbus implementation in terms like validation
      and limits checking, nor is it as tested.
      Its can be useful to test gdbus if dbus-daemon is not availible, but
      its main reason for existance is to implement a default session bus
      on win32 so that e.g. GApplication is guaranteed to work.
      (cherry picked from commit 25581738)
  2. 12 Apr, 2012 1 commit
  3. 11 Apr, 2012 1 commit
  4. 31 Mar, 2012 1 commit
  5. 18 Mar, 2012 1 commit
  6. 10 Feb, 2012 1 commit
  7. 02 Feb, 2012 1 commit
  8. 30 Jan, 2012 3 commits
  9. 26 Jan, 2012 1 commit
  10. 23 Jan, 2012 1 commit
    • Matthias Clasen's avatar
      Add a resource tool · 716cf355
      Matthias Clasen authored
      This lets you poke at resources in elf files and
      standalone resource bundles. So far, only listing
      and extracting resources is supported. The support
      for elf files requires libelf.
  11. 13 Jan, 2012 3 commits
    • Alexander Larsson's avatar
      Support resource:/// uris · e041843b
      Alexander Larsson authored
    • Alexander Larsson's avatar
      Initial version of glib-compile-resources · 82765749
      Alexander Larsson authored
      This is the basic utility to create resource files, either binary
      versions or source files that can be compiled into your app.
    • Alexander Larsson's avatar
      Initial version of GResource · b87cf491
      Alexander Larsson authored
      GResource is a bundle of files combined into a single binary blog.
      The API lets you access the files the resource contains by
      using resource paths. You can also register resources with a
      global list and access these globally in a merged resource namespace.
      The normal way this is used is to link in the resources into your
      application/library and have it be automatically registred.
      Resources are compiled from an xml description using
  12. 02 Jan, 2012 1 commit
  13. 17 Dec, 2011 1 commit
    • Allison Karlitskaya's avatar
      introduce GRemoteActionGroup · eefd0899
      Allison Karlitskaya authored
      This interfaceifies the extra functions that were on GDBusActionGroup
      for dealing with platform data.
      The two main benefits of doing this:
        - no longer have to do a silly song and dance in GApplication to avoid
          calling GDBusActionGroup API from non-dbus-aware code
        - the interface can be reused by the action group exporter to avoid
          ugly and unbindable hook callbacks
  14. 10 Dec, 2011 1 commit
  15. 08 Dec, 2011 9 commits
  16. 21 Nov, 2011 1 commit
    • Chun-wei Fan's avatar
      gio/Makefile.am · 3aeddaa2
      Chun-wei Fan authored
      Filter out yet another *nix only source file from the Visual C++ project
      file completion rules.
  17. 17 Nov, 2011 2 commits
  18. 14 Nov, 2011 2 commits
  19. 17 Oct, 2011 1 commit
    • Allison Karlitskaya's avatar
      push G_THREADS_MANDATORY over the cliff · b0ab7aba
      Allison Karlitskaya authored
      This was used as an optimisation for the macro hackery that used to live
      in gthread.h.  If a particular library or program knew that it could
      rely on thread support being enabled, it would allow for static
      evaluation of conditionals in some of those macros.
      Since the macros are dead and thread support is now always-on, we can
      get rid of this bit of legacy.
  20. 09 Sep, 2011 3 commits
    • Colin Walters's avatar
      Add glib__private__() API to share between glib,gio; port GWakeup to it · 9bf59d4a
      Colin Walters authored
      Historically we've added random symbols to the public API with warnings
      that they're private; examples are:
      glib_gettext(), glib_pgettext()
      g_thread_functions_for_glib_use, g_thread_use_default_impl, etc.
      And we almost added "GWakeup" to public API just to share between glib and
      This new glib__private__() API exports a hidden vtable, and adds a macro
      GLIB_PRIVATE_CALL() that makes it generally convenient to use.
      This adds an extremely tiny cost for the double indirection; but it has
      the benefit that we don't need to either:
      1) compile the code into both glib and gio (like GWakeup), with the
         inefficiency that implies.
      2) Export a "do not use this" symbol; the serious problem with this is
         that someone CAN use it pretty easily.  Particularly if we document
         it.  It's far, far harder to peek into a structure without a public
         header file.
    • Dan Winship's avatar
      Remove !g_thread_supported() codepaths in gio · 5a30712d
      Dan Winship authored
      In particular, remove the libasyncns import, which was only used by
      GUnixResolver, which is only used when threads are not available.
      Likewise remove GWin32Resolver, and the hacky broken non-threaded
      parts of GIOScheduler.
    • Dan Winship's avatar
      Make threads mandatory · 5bc7729d
      Dan Winship authored
      G_THREADS_ENABLED still exists, but is always defined. It is still
      possible to use libglib without threads, but gobject (and everything
      above it) is now guaranteed to be using threads (as, in fact, it was
      before, since it was accidentally impossible to compile with
  21. 06 Sep, 2011 1 commit
  22. 03 Sep, 2011 1 commit
  23. 25 Aug, 2011 1 commit
  24. 22 Aug, 2011 1 commit
    • Colin Walters's avatar
      GTimeZoneMonitor: Revert addition of this class · 5b68b49b
      Colin Walters authored
      The main rationale for adding it was to avoid having gnome-shell
      mmap'ing /etc/localtime once a second.  However, we can just as easily
      run inotify there, and given no one else was clamoring for a way to
      detect when the time zone changes, I don't see a need for public API
      here - at least not yet.
      In the bigger picture, I just don't believe that the vast majority of
      applications are going to go out of their way to instantiate and keep
      around a random GTimeZoneMonitor class.  And if they do, it's has the
      side effect that for other bits of code in the process, local GDateTime
      instances may start varying again!
      So, if code can't rely on local GDateTime instances being in a
      consistent state anyways, let's just do that always.  The
      documentation now says that this is the case.  Applications have
      always been able to work in a consistent local time zone by
      instantiating a zone and then using it for GDateTime constructors.
      We fix the "gnome-shell stats /etc/localtime once a second" issue by
      using timerfd (in glib) and inotify (in gnome-shell).