- Drop gtk-doc internal links
- Escape XML elements

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.

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.

Remove all the old 2.x and 3.x version annotations.
GTK+ 4 is a new start, and from the perspective of a
GTK+ 4 developer all these APIs have been around since
the beginning.

Erika authored Dec 06, 2015 and Matthias Clasen committed Dec 07, 2015

The function can return NULL.

https://bugzilla.gnome.org/show_bug.cgi?id=759081

Instead of issuing g_warning, fill the provided GError.
This lets us test this error handling, and is the right
thing to do. Use the new GtkBuilder helpers and
g_markup_collect_attributes to do so.

Without this information introspection-based consumers don't realize
they can include context information, but instead think that they
receive an extra gpointer argument (which they don't know how to
handle).

https://bugzilla.gnome.org/show_bug.cgi?id=730745

Instead of Return value:

Without sgml mode, we can't escape /* as /* anymore,
so just switch to // for comments in examples.

With all element markup gone, it is time to turn off
sgml mode, and get rid of entities as well.

Specifically, switch to using markdown syntax for sections.

https://bugzilla.gnome.org/show_bug.cgi?id=723119

https://bugzilla.gnome.org/show_bug.cgi?id=723119

It is a little heavy handed. The text can speak for itself.

Use g_string_assign to avoid issues with assigning GString's internal
buffer back to the same string. This can happen when no translations are
available and _gtk_builder_parser_translate returns back the same
pointer that was passed in.

This fixes a regression from commit e9f182e3
that caused GtkComboBoxText <items> from GtkBuilder to show up empty if
no translations are available.

https://bugzilla.gnome.org/show_bug.cgi?id=700629

Pointed out in https://bugzilla.gnome.org/show_bug.cgi?id=699016
The fix here is slightly different. We make
_gtk_builder_parser_translate return a const char * instead of
a dup'ed string, and fix up the callers.

Instead of an explicit { 0, } when declaring the variable.

Mostly making sure that return values and varargs don't loose
their docs.

Fixed GtkCellLayout buildable implementation to set cell properties explicitly set to "" (i.e. explicitly set to nothing).

I've decided that it is isn't feasible to make cell areas runtime-settable
in the time we have left before 3.0, therefore, I'm going with the
approach to allow init() functions to instantiate the default cell area
and issue a warning if a construct property is ignored.

This is not ideal, but it keeps existing icon view and combo box
subclasses working.

https://bugzilla.gnome.org/show_bug.cgi?id=639139

The fact that GtkCellLayout was checking "if (gtk_cell_layout_get_area (layout))"
and executing code contitionally from the apis instead of simply falling
back to the default implementation for these things was causing problems
in language bindings such as gtkmm... Regardless, the implementation
is cleaner this way too.

Return value was copied and pasted from gtk_cell_layout_get_cells(),
which is obviously wrong.