1. 22 May, 2021 1 commit
  2. 21 May, 2021 1 commit
    • Matthias Clasen's avatar
      docs: Reduce redundancy · 4a0d3d7a
      Matthias Clasen authored
      Remove a boatload of "or %NULL" from nullable parameters
      and return values. gi-docgen generates suitable text from
      the annotation that we don't need to duplicate.
      This adds a few missing nullable annotations too.
  3. 20 May, 2021 2 commits
  4. 11 Mar, 2021 2 commits
  5. 01 Dec, 2020 1 commit
  6. 14 Oct, 2020 1 commit
  7. 12 Sep, 2020 1 commit
    • Matthias Clasen's avatar
      Clean up lots of GTK+ -> GTK · 929a56e5
      Matthias Clasen authored
      Replace most remaining uses of GTK+ in the docs and
      user-visible strings by GTK. Also remove some leftover
      "Was added in 3.x" sentences from the docs.
  8. 15 Aug, 2020 1 commit
  9. 14 Aug, 2020 1 commit
    • Matthias Clasen's avatar
      Drop style class defines · ae7cefd9
      Matthias Clasen authored
      We document the supported style classes by name,
      not by macro name, and these macros don't really
      add any value. Drop them for GTK 4.
  10. 26 Jul, 2020 1 commit
    • Emmanuele Bassi's avatar
      Remove ATK · c63087a5
      Emmanuele Bassi authored
      To build a better world sometimes means having to tear the old one down.
              -- Alexander Pierce, "Captain America: The Winter Soldier"
      ATK served us well for nearly 20 years, but the world has changed, and
      GTK has changed with it. Now ATK is mostly a hindrance towards improving
      the accessibility stack:
       - it maps to a very specific implementation, AT-SPI, which is Linux and
         Unix specific
       - it requires implementing the same functionality in three different
         layers of the stack: AT-SPI, ATK, and GTK
       - only GTK uses it; every other Linux and Unix toolkit and application
         talks to AT-SPI directly, including assistive technologies
      Sadly, we cannot incrementally port GTK to a new accessibility stack;
      since ATK insulates us entirely from the underlying implementation, we
      cannot replace it piecemeal. Instead, we're going to remove everything
      and then incrementally build on a clean slate:
       - add an "accessible" interface, implemented by GTK objects directly,
         which describe the accessible role and state changes for every UI
       - add an "assistive technology context" to proxy a native accessibility
         API, and assign it to every widget
       - implement the AT context depending on the platform
      For more information, see: #2833
  11. 24 Jul, 2020 2 commits
  12. 20 May, 2020 2 commits
  13. 12 May, 2020 2 commits
  14. 05 May, 2020 2 commits
    • Matthias Clasen's avatar
      assistant: Drop the Private struct · cda1a25a
      Matthias Clasen authored
    • Matthias Clasen's avatar
      window: Derive from GtkWidget · 9a65ed9a
      Matthias Clasen authored
      We want to remove GtkBin and GtkContainer as they don't
      provide much useful functionality anymore. This requires
      us to move get_request_mode and compute_expand down.
      Update the accessible implementation to match, remove
      remnants of container implementations in GtkWindow
      subclasses, and fix livecycle issues around destroy
      vs dispose in GtkAssistant.
      After this commit, using gtk_container_add on window
      subclasses is not allowed anymore, but adding childing
      with <child> in ui files still works.
      See #2681
  15. 28 Apr, 2020 1 commit
  16. 10 Apr, 2020 1 commit
  17. 26 Mar, 2020 1 commit
  18. 19 Mar, 2020 2 commits
  19. 10 Sep, 2019 1 commit
  20. 25 Aug, 2019 1 commit
  21. 31 May, 2019 1 commit
    • Christian Hergert's avatar
      gtk: rely on default marshallers · bd26cce8
      Christian Hergert authored
      Similar to previous removals of g_cclosure_marshal_VOID__VOID we can remove
      other marshallers for which are a simple G_TYPE_NONE with single parameter.
      In those cases, GLib will setup both a c_marshaller and va_marshaller for
      us. Before this commit, we would not get a va_marshaller because the
      c_marshaller is set.
      Related to Initiatives#10
  22. 29 May, 2019 1 commit
    • Christian Hergert's avatar
      marshallers: ensure g_cclosure_marshal_VOID__VOIDv is used · f507a790
      Christian Hergert authored
      If we set c_marshaller manually, then g_signal_newv() will not setup a
      va_marshaller for us. However, if we provide c_marshaller as NULL, it will
      setup both the c_marshaller (to g_cclosure_marshal_VOID__VOID) and
      va_marshaller (to g_cclosure_marshal_VOID__VOIDv) for us.
  23. 28 May, 2019 1 commit
  24. 27 May, 2019 2 commits
  25. 28 Apr, 2019 1 commit
  26. 19 Mar, 2019 1 commit
  27. 21 Feb, 2019 2 commits
  28. 15 Feb, 2019 3 commits
  29. 13 Feb, 2019 1 commit