GitLab

This avoids to make the rows white on a white background and make the
actual preferences easier to see.

This will allow the window to reach narrow widths.

This makes sure the window isn't stupidly small by default.

This also sorts the sections alphabetically.

This is needed to access HdyPreferencesWindow and HdyHeaderBar.

see GNOME/epiphany#771

Currently it looks like an asynchronous function, but it actually does
sync I/O, which is bad.

This also requires also making ephy_bookmarks_export() async, which
required adding gvdb_table_write_contents_async(), which I upstreamed to
GVDB. (It was added to Epiphany in the previous commit.)

It also requires adding GCancellable parameters where required, to avoid
introducing new crashes. This means we need a way for external code to
access the EphyBookmarkManager's cancellable or we would need to get rid
of the warn_on_error convenience callback.

Also, remove ephy_bookmarks_manager_load_from_file(), since it's only
one line long and only used in one place.

Finally, rename the functions according to Carlos's feedback.

Fixes #336

In particular, this adds gvdb_table_write_contents_async() from gvdb!4.

It also requires changing some integer types due to an API break in
gvdb_table_get_names().

This makes the code more in line with the coding style.

This aligns the look of the header bar of the history dialog to the one
of the cookies dialog.

This simplifies the code and moves the date between the title and the
separator as the previous design can't be implemented via HdyActionRow.

This also fixes a memory leak as the "title" and "url" data were set
without a destructor and we stop using them.

Show better looking panels when the history is empty and when the search
gave no results.

This avoids it to appear full of nothing if there are not enough
elements to fill the window's height.

This simplifies the code a bit.

Although #713 is fixed for new users, anyone who previously suffered
from a broken web app migration is doomed to eternal crashes. We
probably can't reasonably recover the broken profile dir, but we should
at least try to warn users what is going on.

We free with the wrong free function

It's already a dependency of libephymain, but not of the rest of the
code, which is causing a bunch of build failures on the CI.

This is for web apps only, and only if they are migrated before the
default profile. The first attempt to run the web app after migration
will fail, and it will need to be started a second time in order to pick
up the new profile dir in the modified desktop file. This is pretty
unfortunate, but difficult to avoid.

The legacy profile dir just returns the current profile dir, or the
legacy default profile dir when run without a profile dir. That's
obviously not correct since the legacy profile dir is not necessarily
the current profile dir. It leads to some harmless but unexpected
behavior, and it's fragile. Sadly this is not straightforward to
implement correctly, so just add a FIXME for now.