On 03/08/2011 09:53 AM, Ivan Cukic wrote: > Hi all, > > First of all, one thing to mention - KDE apps are not advised to use > QtZeitgeist directly because that way the 'tracking' has no idea about the > activities. > > File/resource tracking (and thus rating) should be per activity - as an > example, there is no point in showing java docs that you used in > 'Developing J2EE application' activity in a 'KDE development activity'. > > The classes that should be used are KActivity* which will soon enter > kdelibs/experimental. > > The activity manager (the dbus service behind KActivity classes) will have > both Zeitgeist and Nepomuk as backends. (both as optional deps) > > --- > > Zeitgeist vs Nepomuk > > Sebastian concluded that storing all the events in Nepomuk wouldn't be > wise, so it was agreed to store them in Zeitgeist which was designed with > that sole purpose.
to be precise: I wanted to test storing all in Nepomuk first which I have not done yet. > My current intention is the following (for the activity manager) > - Store all events in Zeitgeist making it possible to have more advanced > queries like 'files opened last week between tue and sat in the > ewening' > - Store only per-activity scores in nepomuk making it possible to have > 'which are the most common files opened in kate during some activity' how do you do that? Cheers, Sebastian > > After this, we can do all kinds of magic even if not both Z and N are > running. > > Cheerio, > Ivan > > >