← Back to team overview

gnome-zeitgeist-users team mailing list archive

GNOME Activity Journal 0.3.4 released


On behalf of the GNOME Activity Journal team and the Zeitgeist Project
I am happy to announce the release of GNOME Activity Journal 0.3.4.
Since the previous release there has been a major overhaul to allow
the journal to display Zeitgeist events which lack a local file as its
subject. This means that, with the correct data-source installed,
Journal now displays web-page visits, tomboy notes, telepathy
conversations, and anything else submitted to the Zeitgeist log.

What is GNOME Activity Journal?
GNOME Activity Journal is not a File Browser but an Activity Browser.
It uses the ZeitgeistFramework to display what you did and introduces
a better way of finding the things that you were doing quickly.

* Downloads: http://edge.launchpad.net/gnome-activity-journal/0.3/0.3.4/+download/gnome-activity-journal-0.3.4.tar.gz
* About Zeitgeist: http://zeitgeist-project.com
* Wiki: http://live.gnome.org/GnomeActivityJournal

New Since 0.3.3

- New timeline view that now based on a gtktreeview.
- Revamped multiple day view
- Better support for Dark themes
- Widgets using themes with pixbuf backgrounds are now drawn correctly
- Added a More Information window which displays a description of the
event, its subject, and other events related to the event.
- Context menu now works in all widgets
- Improved rendering in thumbnail view

- Added a content object system which allows users to launch, view,
and manipulate events with non-file subjects.
- Improved event request, and related event results.

What to expect with the next releases
With the release of Zeitgeist 0.3.3 comes a good API which provides
all the features currently required by a application like Activity
Journal. Since we can expect these features to remain in subsequent
versions of Zeitgeist, Activity Journal's release cycle and
development are no longer strongly dependent on a development version
of Zeitgeist.

Some of the planned underlying work includes:
- New architecture which separates a persistent storage model from the view.
- Improved performance by caching events, and reducing the amount of
data requested over DBus.
- Specialized support for more data-sources