User questionnaire (or Poll): Usage tracking [Lancelot]

Functional Programming in C++

Published by Ivan Čukić in the KDE development section, on 24 March 2009

Since I’m planning to make the Favourites section a bit smarter sometime in the future (something like Amarok’s score/rating system), but it will not happen in time for KDE 4.3, I’ve come up with an idea of tracking the user’s (your) behaviour and to record which applications you start. And, maybe, which item you choose from the list when you search for something.

Before you start throwing rocks at me, here are some details about the idea.

It would be local only. The collected data would not be sent anywhere and would remain in your .kde directory for all times. It would be optional. Though I don’t know whether to turn it on by default or not. In any case, I think some “what’s new / set up the new features” notification would be needed.
The data would not be used in the KDE 4.3 version, but in a later one.

So, in a nutshell, it would collect the data which would be used once the Favourites section becomes smart.

My questions here are:

Should the tracking be turned off by default? *
Should it be implemented at all before the Fav section gets smarter?
Note that once the Fav section does become smart, it will be changed to ‘on by default’.

So, let me know what you think about this…

Stephen
No harm in turning it on by default.
Angel Blue01
Turn it on by default
TheBlackCat
If there is something going wrong with usage tracking it would probably be better to know back when it is unimportant rather than when Lancelot depends on it. So I would say turn it on by default, and put up some comments telling people what it should be doing sot hey can test it if they want.
hallowname
Great idea.
Software should know as much as possible about the user in order to best serve the user.
openbrain records input-output pairs to local. I have to weigh which thoughts need fixing the most.
on by default sounds like the best way to learn how to best implement the 'intelligent favorites' you envision :)
Azungu
Could this be integrated with a nepomuk store so the information is available to other applications? Just a thought.. otherwise great work!
dog
Turn on by default, and implement ASAP so there will by more data and favorites will by smarter when available. +1
jscurtu
Awsome.. I would also say on by default ..
mandata
Another Vote for ON by default
lawal adekunle
That's a great idea anything to make lancelot better is always welcome. Though the user still has the final say but i for one would allow it.
Ivan Čukić
@<a href="#comment-8075" rel="nofollow">Jeff</a>: There are two answers to this question. 1. No. 2. No, and it shouldn't. I considered that before and came up with a conclusion that listening to other launchers is not needed (krunner may be needed*). And, here is why - if you start an application by an icon on panel/desktop or some other way, there is really no need to add it to favourites too. (this is in a nutshell)
* Concerning KRunner, Lancelot provides all KRunner features, that is, all features the standard 'command oriented' KRunner does.
Ivan Čukić
@<a href="#comment-8032" rel="nofollow">notKlaatu</a>: Yes, you'll be able to choose the favourites just like you can now. The /smart/ will be to fill the favourites with extra items automatically. (usage frequency, last time used... maybe even part of the day like Raptor guys wanted...)
Jeff
I'm all for on by default. I do have a question, though: are application launchers aware of the activity of other application launchers?
Maybe I should elaborate. I primarily use krunner to launch my applications - probably nine times out of ten. I still use Lancelot and/or Kickoff, but fairly infrequently. Does Lancelot have a way to see what I launch from Krunner and use that data to help shape the "Favorites" tab?
notKlaatu
on by default... with the caveat that it should not, of course, override my ability to add my own favourites..? i can appreciate a "most often used" section in Favourites, but I'd obviously want the ability to add something that is not most-often used just in case i want it there for when i need it.