GitLab

All fields (or groups) that we could not get the information for
will be just omitted from the json, because that is intended to be
read by machines and that the absence of the field better
communicates the absence of information.

Explicitly make note if we could obtain that information so we can
act on that later.

With the previous patch a call to g_object_get of these properties
will still return 'Unknown'.

The helper will also handle the case when the value is NULL,
preparing for a future changes when info fields can be unset if
the information for them could not be obtained.

Report unknown if a string property is NULL. This makes it possible
to avoid setting all fields to 'Unknown' in the various functions
that fill in the system information.

This will enable us to distinguish between X11 and Wayland, which
might reveal important differences in power consumption in those
too.

Use bulk property installation via g_object_class_install_properties.

Uses gdk to get monitor information, tries to identify the builtin
monitor via the model string; if that fails uses the primary one,
and finally falls back to the first if none of that works.

In the case there we have less then 3 components for the kernel
we return the un-split string, but we need to make a copy of it
before.

Unbreaks the build. Ups.

If getting the renderer via the session fails, we can use a helper
binary provided by gnome-session to get the information.

Therefore we can simplify the code. The minimal interval we need
to wait to see any changes is UPDATE_FREQUENCY.

We are not reading it anymore anyway; everything is based on energy.

Having timestamps makes gbb significantly more useful for logging
because you can record and then later retrace what was happening.

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

We really support "energy" properly, so no need to pretend to
do for "capacity".

If the corresponding sys devices/entries are missing we should
still get 'Unknown' in the fields, but the fields should be
present.

Not only useful for humans, but also to synchronize the tests, i.e.
as an indicator when the monitor binary is started and delivering
notifications.

Currently only runs gbb info --json and checks that the simulated
battery has the right vendor and model.

We are now returning only energy values from GbbBattery, so we can
get rid of the charge related fields/functions/calculations from
everywhere that is not the GbbBattery itself.

That is, also return GbbMains, and rename it to
gbb_power_supply_discover.