Historisation
Raptor shouldn't weight all the clicks the same. Instead, it should weight them by monthly periods, so that current clicks are worth more than clicks of the last month. Five fields are used:
Field Description Weighting
CurM Current Month 1.0
LasM Last Month 0.8
2MB Two Months Back 0.6
3MB Three Months Back 0.4
4MB Four Months Back 0.2
Everytime the user starts his computer and KDE, raptor checks when it was last loaded. If this was not in the current month - e.g. 2 months ago - it moves the click value to the respective field, here 2MB, and sets the more current fields (here LasM and CurM) to 0. It also moves the values of the other fields back, here 2MB to 3MB, 3MB to 4MB.
Of course the developer needs to take care that he reads the column 2MB first and saves it to a variable, before overwriting it.
When the user now clicks on an element, the current value in the CurM field of the respective application is increased by one. We do NOT save every click with a date, but only the cumulated clicks per month, due to performance reasons in the XML and because we don't want to blow up the file.
Possible Problems:
