GitLab

This makes it simple to use Libhandy's widget from within glade without
installing the library.

See https://developer.gnome.org/gladeui/stable/catalogintro.html

The dialer was not emitting notify signals when the number GObject
property was set.  The property is flagged with
G_PARAM_EXPLICIT_NOTIFY.  We fix this by emitting the signal in
hdy_dialer_set_property.  And adding a test to check.

The number property is currently being overwritten, meaning any excess
characters in the previous number will remain.  To fix this, we assign
instead.  And add some tests to check.

Libhandy is (and never was) intended for dialers only.

Replace the boolean 'folded' property by the HdyFold 'fold' property.
This helps making the code more readable by using a properly defined
type rather than generic values for the fold state.

This will be used in the next commit to better represent the fold of a
HdyLeaflet. This makes the typing stronger and improves the readability
of the code by expliciting the values more than a boolean does.

This adds a missing tranfer annotation to avoid a build warning.

An application will likely want to display it's own thing so don't hard
code it in the keypad.

Require HANDY_USE_UNSTABLE_API to be defined to use handy.h, forcing the
users of libhandy to acknowledge that the API may break in the future.

Replace calls to g_test_init() and gtk_init() by calls to
gtk_test_init().

This better reflects the goal (testing GTK+ code), this makes the code
simpler and it does a bit more to make the tests deterministic like
setting the locale to C. This also allows us to automatically benefit
from improvements and fixes in the GTK+ test initialization process.

This is copied from GTK+ 3.22 because it is private there. It will be
used in the next commit to implement HdyStackableBox's transition
animations.

GObject always have a dispose handler so objects derived
from it don't need to check for that.

Even if we do it here in end_cycle, it's better to cleanup close
to the code that need it, we protect our code against possible
changes in end_cycle.

- The first enum with no value is implicitly assigned to 0
- static storage values are initialised with 0/NULL values

No need for a null check here

- parameters alignment
- space between function name and parameters list

There's no references to the hdy-dialer-button module in both
hdy-string-utf8.[c|h] so let's remove the corresponding #include.

 - add a space between function name and parameters list.
 - add a colons to the identifier name in gtk-doc comments
   (not mandatory till we have annotations, but it's the usual syntax)
 - only one empty line between each function body.