Federico we monitor GtkRecentlyUsed now directly We subscribe to its events. But tbh it needs some work since GtkRecentInfo timestamps are messed up. A visit timestamp for example is interpreted by GtkRecentInfo as (open or close) while a modfiy timestamp is (modfiy + close). Cheers Seif
On Wed, May 4, 2011 at 4:13 AM, Federico Mena Quintero <[email protected]>wrote: > On Tue, 2011-05-03 at 19:32 -0400, Colin Walters wrote: > > > If we're modifying applications, the focus should be on adding API to > > GTK+ to accommodate whatever it is the design calls for. In this > > case, GtkRecentManager seems like a good fit. > > "Normal" apps which deal with files already use GtkRecentManager to log > the files you edit. Zeitgeist in turn monitors your > ~/.recently-used.xbel and populates its log from it. So, those apps > don't need changes. > > It's certainly possible to modify GtkRecentManager to log to Zeitgeist > directly, and keep it as a wrapper API. But for now, things work > perfectly as they are. > > Apps which don't deal in files don't use GtkRecentManager, and *those* > do require changes to log to Zeitgeist directly. Web browsers, IM > clients, etc. The Zeitgeist-dataproviders are exactly this kind of > extensions to various apps. > > Federico > > _______________________________________________ > gnome-shell-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-shell-list >
_______________________________________________ gnome-shell-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-shell-list
