By storing the timestamp of the day in the database we can significantly
reduce the calls to localtime, which should result in a noticible
speedup.
We are changing the database format. For the convenience of the user
the code automatically converts from the old format.
Loading history items used to involve frequent calls to
localtime() and g_memdup(). We avoid this by storing the
date strings in parent items now, which can even be used to
display items in the treeview.
Deleting of treeview items was also reworked so it should
work from menu items and the panel.
The diagnostic dialog actually performs better now
because we do the extension loading and session setup
in idle callbacks, aside from the code being more
easily readable in smaller units.
We are not literally undoing in the sense of
reverting, this is actually about undoing
the individual parts of the last refactoring
that implemented the socket/ plug logic.
As turned out, the idea was nice but the
implementation was absolutely not, embedding
of processes in a graphical way is not
at all reliable enough for complex use cases.
Naturally this change should solve all sorts
of peculiar issues, including actual
regressions in functionality. Relieving.
The approach is rather plump, Midori can be
run in a plug mode that creates a GtkPlug,
while the normal instance knows how to embed it.
Communication between browser and tabs is
done via named pipes which are portable.
The feature is not complete right now, there
are expected regressions, but it works.
As a bonus, we implement Not found pages.
Originally menu items could in some cases become as wide as
the whole screen, making working with menus rather hard.
Now we ellipsize at 50 characters in the middle of the string.
Apparently lots of users cannot use Midori
after this change and with no way to track down
the cause of the issue, let's just not use this.
The check was only for minimal gain anyway
