[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors

2010-09-25 Thread Seif Lotfy
** Branch linked: lp:~zeitgeist/zeitgeist/fix-646124 ** Changed in: zeitgeist Status: Triaged = In Progress -- Wrong understanding of the LeastRecentActors https://bugs.launchpad.net/bugs/646124 You received this bug notification because you are a member of Zeitgeist Framework Team,

[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors

2010-09-25 Thread Seif Lotfy
** Changed in: zeitgeist Status: In Progress = Fix Committed ** Changed in: zeitgeist Milestone: 0.6 = 0.5.2 -- Wrong understanding of the LeastRecentActors https://bugs.launchpad.net/bugs/646124 You received this bug notification because you are a member of Zeitgeist Framework Team,

[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors

2010-09-24 Thread Mikkel Kamstrup Erlandsen
Taking the LeastRecentSubjects example. I'm going to assume you have time=0 on the left and time0 on the right: 1, 2, 1, 3, 4. Then One event for each subject only, ordered with oldest events first would definitely mean: 1, 2, 3, 4. If we are sorting like RainCT is proposing then the docstring

[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors

2010-09-24 Thread Seif Lotfy
Exactly. The current docstring matches the current returns. IMHO both are wrong according to my and Siegfried's definition of LeastRecentActor. I do agree with your proposal of changing the docstring to The most recent event for each subject, ordered with the oldest events first. Because it

[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors

2010-09-24 Thread Markus Korn
Seif, can you please give tow different usecases, one for the old definition of LeastRecentActors and one for your new one. Please also try to explain how changing the definition will influence real world usecases. -- Wrong understanding of the LeastRecentActors

Re: [Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors

2010-09-24 Thread Seif Lotfy
On Fri, Sep 24, 2010 at 12:37 PM, Markus Korn thek...@gmx.de wrote: Seif, can you please give tow different usecases, one for the old definition of LeastRecentActors and one for your new one. Please also try to explain how changing the definition will influence real world usecases. --

[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors

2010-09-24 Thread Markus Korn
Ok, maybe there were some misunderstandings, I was looking for some real life questions... Let's assume this one: What were the first three actors accessing '/home/markus/seif.txt' With the current definition of LeastRecentActors the query would look like template =

Re: [Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors

2010-09-24 Thread Siegfried Gevatter
2010/9/24 Markus Korn thek...@gmx.de:  * Can you give me a similar question which gives a usecase for your definition? Which were the applications I haven't used for the most time? -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer       363DEAE3 -- Wrong understanding of

[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors

2010-09-24 Thread Markus Korn
We discussed this issue on IRC, a summary: * the current definition of LeastRecentActors is wrong, it should be application I have not used for the longest time * we need a new ResultType for the old definition (The first event of each different actor), something like OldestActor The plan to