| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Instead of hardcoding all visits as 'TYPED' properly distinguish
between bookmarks, following links and typing URIs in the entry.
We'll use this to compute the frecency of history items.
|
|
|
|
|
|
|
|
|
|
|
| |
The main purpose of the cancellable API in ephy-history-service
is to let the user notify when the results of the operation
are no longer needed and the callback call can be omitted. Since
performing a read operation, in such cases, makes no sense, we
cancel them altogether. However, given the nature of the service,
we don't cancel write operations.
https://bugzilla.gnome.org/show_bug.cgi?id=671901
|
|
|
|
|
| |
By now, the public API only supports filtering by time range, but
filtering by string matching is also possible.
|
|
|
|
| |
This method will remove all the history related to that host.
|
| |
|
|
|
|
| |
To retrieve all hosts in the history
|
| |
|
|
|
|
|
|
|
|
|
| |
Similar to the old EphyHistory 'add-page' signal. It allows blocking
the visit by handling the signal, since the actual logic to add the
visit is in the class' default handler.
The add_visit(s) methods won't emit this signal, but for now we'll
assume that whoever is using those knows what he's doing.
|
|
|
|
| |
Fits much better with the naming model in that class.
|
|
|
|
|
|
| |
It was a very thin wrapper on top of the history service, it does not
seem to make much sense. For now move the two useful helper methods
down to the service without further changes.
|
|
|
|
| |
It's not really that useful.
|
|
|
|
|
|
|
|
|
|
| |
Zoom levels have always been stored per host in Epiphany, not per URL
(otherwise you'd have to re-apply the zoom level again and again when
visiting, say, every news entry in your favorite newspaper). Change
things to work like that.
Note: this changes the SQL table format for the history, so you'll
need to re-migrate your history.
|
|
EphyHistoryService provides a high-level API to store history
information. It will processed by a worker thread using SQLite to
provide a fast, responsive service to the main UI.
Based on the code by Martin Robinson (mrobinson@igalia.com) and
Claudio Saavedra (csaavedra@igalia.com).
|