On Thursday 16 January 2014 13:29:23 Barros Pena, Belen wrote: > On 16/01/2014 12:25, "Ravi Chintakunta" <[email protected]> > wrote: > >While I am writing the base code for filtering objects in a table, I > >cannot think of a use case where one would be interested in filtering > >tasks by their execution order. Please refer to the UI design in page 8 > >of the attachment in > >https://bugzilla.yoctoproject.org/show_bug.cgi?id=4278. > > > >Filtering tasks between two arbitrary numbers does not seem to serve any > >purpose. Am I missing something? > > I guess the question is that the numbers don't need to be arbitrary. If I > am looking at the details of a task x, and I see its order number is n, I > might be interested in looking at what happened right before and after n, > and I might find useful to narrow down the content of the massive tasks > table to n-5 to n+5, for example, so that I can focus on the interesting > subset without being bothered by the noise of the other tasks. > > Having said that, I am very much open to change. If people do agree that > filtering tasks by their execution order is not useful, let's get rid of > that filter.
I hadn't yet added my 2c, but for what it's worth I agree with Ravi - I don't see much use in filtering on execution order particularly if it will take us extra time to implement. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
