This resolves various indirections, and since we are always
using the action anyway, we finally move all logic to one
place. There should be room for optimizations now.
Incidentally this also keeps the completion intact if
the entry needs to be recreated.
For the moment, a define in the code decides whether items
are sorted based on when they were added or how often
a page was visited. The 'visits' property and respective
database column is unused (we keep it for compatibility).
It turns out it's enough to store that information in
the tree model.
The visit based sorting is not enabled because it is
simply delaying startup incredibly. It will have to be
decided whether to introduce a preference, or always use
a visited based sorting once the startup delay is fixed.
History items are also deleted from the tree model now
if they are too old, according to the preference.
This is a step towards customziable toolbars.
The new action actually provides a nicer API than
MidoriLocationEntry does right now. Later we
should improve the widget itself as well.
There are still to resolve regressions:
- The location icon tends to be initially empty
- The news feed icon doesn't show up
- Tab icons sometimes load and reset again afterwards
