GitLab

Replace leftover gtk-doc syntax (#Type) with backquotes.

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.

allow-none has been deprecated for a long time
already. Instead use optional and nullable everywhere.

Mostly fixing up indentation of continuation lines,
and other small cleanups.

Matthias Clasen authored Feb 26, 2021 and Emmanuele Bassi committed Mar 11, 2021

Convert link syntax, an example image, clean things up.

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.

Changed the wording to improve the clarity of the documentation. Fixed grammar issue ("spllited")

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.

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

And add style classes to differentiate them

When GtkContainer goes away, we don't have
an "add" signal anymore.

These are all on GtkBox or enumerating children.

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

Now that we can have an element-type annotation, we should use it where
needed.

Replace most uses of gtk_style_context_add/remove_class
by the new APIs. The only remaining uses of the old API
are in save/restore situations.

This reverts commit 3ac4c76b, reversing
changes made to 6ec96d2e.

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

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.

Replace gtk_widget_grab_default by gtk_window_set_default_widget.

And make sure it's included everywhere it's needed.

Otherwise, bad things can happen later, if
somebody holds onto the list model.

This is causing us some internal complications, and
it is very easy to just add padding to the pages
yourself.

We don't use any non-stack features of the notebook here.

Without this, introspection complains about a missing
transfer annotation.

This is mainly useful to make the page objects
accessible in the inspector.