Google Git
Sign in
fuchsia / third_party / glib / refs/heads/upstream/wip/hadess/gapp-restart-data
commit3a113699d7a3076c16b7a249a40f80c5f751959e[log] [tgz]
authorBastien Nocera <hadess@hadess.net>Wed Feb 20 01:39:10 2019 +0100
committerPhilip Withnall <pwithnall@endlessos.org>Mon Jul 17 15:20:50 2023 +0100
tree5df52185f09aa2aa576367223922146d2b30bacc
parent741a561c4daf2ab02ad613456f130719fe97435c [diff]
GApplication: Add RestartData property, and setter

The RestartData property on the org.gtk.Application interface can be
used by session services to save some data to disk should the
application disappear.

The application would call g_application_set_restart_data() when the
state of the application changes, with enough information for the
application to restart itself in the same "position".

FIXME:
 [ ] API docs
 [ ] note about restart data size
 [ ] have one example implementation of the session side

One idea would be for xdg-desktop-portal to save a stringified
RestartData to ~/.var/app/$ID/config/state.gvariant if none empty when
the application disappears from the bus.

Questions:
- Can we enforce to only do this for unique applications?
- Can we detect applications leaving the bus suddenly, or do we
  want to rely on them clearing RestartData if they're "done" (or should
  they always save state, *some* state)
- Should we implement this via org.gnome.SessionManager.Client and the
  app calling out to gnome-session instead?
- Or is this API fine, and gnome-session can do what xdg-desktop-portal
  does above?
5 files changed
tree: 5df52185f09aa2aa576367223922146d2b30bacc
  1. .gitlab-ci/
  2. .reuse/
  3. docs/
  4. fuzzing/
  5. gio/
  6. glib/
  7. gmodule/
  8. gobject/
  9. gthread/
  10. LICENSES/
  11. m4macros/
  12. po/
  13. subprojects/
  14. tests/
  15. tools/
  16. COPYING ⇨ LICENSES/LGPL-2.1-or-later.txt
  17. .clang-format
  18. .dir-locals.el
  19. .editorconfig
  20. .gitignore
  21. .gitlab-ci.yml
  22. .gitmodules
  23. .lcovrc
  24. CODE_OF_CONDUCT.md
  25. CONTRIBUTING.md
  26. glib.doap
  27. INSTALL.md
  28. meson.build
  29. meson_options.txt
  30. NEWS
  31. README.md
  32. SECURITY.md
README.md

GLib

GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.

The official download locations are: https://download.gnome.org/sources/glib

The official web site is: https://www.gtk.org/

Installation

See the file ‘INSTALL.md’. There is separate and more in-depth documentation for building GLib on Windows.

Supported versions

Only the most recent unstable and stable release series are supported. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.

See SECURITY.md for more details.

Documentation

API documentation is available online for GLib for the:

Discussion

If you have a question about how to use GLib, seek help on GNOME’s Discourse instance. Alternatively, ask a question on StackOverflow and tag it glib.

Reporting bugs

Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing incoming+gnome-glib-658-issue-@gitlab.gnome.org, but this will give you a degraded experience.

Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums.

In bug reports please include:

  • Information about your system. For instance:
    • What operating system and version
    • For Linux, what version of the C library
    • And anything else you think is relevant.
  • How to reproduce the bug.
    • If you can reproduce it with one of the test programs that are built in the tests/ subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.
  • If the bug was a crash, the exact text that was printed out when the crash occurred.
  • Further information such as stack traces may be useful, but is not necessary.

Contributing to GLib

Please follow the contribution guide to know how to start contributing to GLib.

Patches should be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123):

Closes: #123

Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.