1. 11 May, 2022 1 commit
  2. 31 May, 2021 1 commit
  3. 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.
      4a0d3d7a
  4. 11 Mar, 2021 1 commit
  5. 28 Jan, 2021 1 commit
  6. 03 Jan, 2021 1 commit
  7. 21 Dec, 2020 1 commit
  8. 12 Nov, 2020 1 commit
  9. 11 Nov, 2020 1 commit
  10. 20 Oct, 2020 1 commit
  11. 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
         element
       - 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
      c63087a5
  12. 24 Jul, 2020 2 commits
  13. 05 Jun, 2020 1 commit
    • Emmanuele Bassi's avatar
      Move orientable style classes into GtkWidget · 6e52ef96
      Emmanuele Bassi authored
      It feels slightly wrong to have GtkOrientable operate on widgets, but at
      least what happens when an orientable widget changes orientation should
      be part of GtkWidget.
      
      This will allow to add more state changes without accessing widget state
      from the outside of gtkwidget.c.
      6e52ef96
  14. 12 May, 2020 2 commits
  15. 07 Feb, 2020 1 commit
  16. 28 Jan, 2020 1 commit
  17. 21 Jan, 2020 1 commit
  18. 09 Sep, 2019 1 commit
  19. 28 May, 2019 1 commit
  20. 06 May, 2019 1 commit
  21. 26 Mar, 2019 1 commit
  22. 05 Feb, 2019 1 commit
  23. 24 Jan, 2019 7 commits
  24. 04 Dec, 2018 1 commit
    • Daniel Boles's avatar
      Box, Grid: Improve various bits of documentation · 72d09d22
      Daniel Boles authored
      Issue #1495 showed that the docs of GtkGrid retain outdated implications
      that (as was once, but is no longer, the case) it is intended to replace
      GtkBox, by discussing HfW and widget properties in a way that suggests
      GtkBox can't handle them. But of course it does, and it's preferable for
      simple single-row/column cases. Worse, we said GtkGrid “provides exactly
      the same functionality” for the latter case, but the original point of
      that Issues was that it doesn’t, at least for CSS positional selectors!
      
      Box:
      • Use an actually meaningful @Short_description.
      • Remove unhelpful @See_also references to unrelated containers.
      • Remove references to “rectangular area”: it might be another shape
        via CSS, or “rectangular” might falsely imply 2 dimensions of children.
      • Mention Orientable:orientation.
      • Emphasise usefulness of :[hv]align for allocating in the other axis.
      • Don’t say that Grid “provides exactly the same functionality” for a
        single row or column, since (A) it is overkill for that case and (B)
        said Issue proved that it *doesn’t* for CSS child order, for example.
      
      Grid:
      • Don’t dwell on widget properties and height-for-width in a way that
        wrongly implies that Box can’t handle those (or Grid can better). In
        fact, just get rid of that bit altogether: Box handles them fine, and
        such wording was only needed years ago for migration from GTK+ 2 to 3.
      • Point to GtkBox as being preferred for the simple row/column use case.
      72d09d22
  25. 13 Nov, 2018 1 commit
  26. 27 Aug, 2018 3 commits
  27. 18 Jun, 2018 1 commit
  28. 05 Apr, 2018 1 commit
  29. 20 Mar, 2018 1 commit
    • Alexander Larsson's avatar
      GtkWidget: Start renaming widget->window · 63e060a2
      Alexander Larsson authored
      This is an automated change doing these command:
      
      git sed -f g gtk_widget_set_has_window gtk_widget_set_has_surface
      git sed -f g gtk_widget_get_has_window gtk_widget_get_has_surface
      git sed -f g gtk_widget_set_parent_window gtk_widget_set_parent_surface
      git sed -f g gtk_widget_get_parent_window gtk_widget_get_parent_surface
      git sed -f g gtk_widget_set_window gtk_widget_set_surface
      git sed -f g gtk_widget_get_window gtk_widget_get_surface
      git sed -f g gtk_widget_register_window gtk_widget_register_surface
      git sed -f g gtk_widget_unregister_window gtk_widget_unregister_surface
      
      git checkout NEWS*
      63e060a2
  30. 09 Feb, 2018 1 commit