[Toaster] making recipes faster

[Barros Pena, Belen]

On 09/04/2014 19:35, "Reyna, David" <david.reyna at windriver.com> wrote:

>Hi Dave,
>
>I agree with your observation. I will though point out that what a user
>really wants is based on the context of what they are doing.
>
>For example, when I first use a tool I usually want very short lists
>because since I do not know what is available nor what I want, so I want
>to browse around as fast as possible. However, as I get more used to a
>tool I tend to want really long lists, because I want to see the
>information in large chunks and paging between is lost time and
>concentration.

I totally agree that the number of entries you want to see is
context-specific: it completely depends on what you are trying to do.
Since we cannot know, I would once again aim for consistency. Right now,
we are defaulting to different numbers across pages: if I remember
correctly, recipes and tasks are defaulting to 100, but builds is
defaulting to 10. I think 25 might be a good default.


>
>I think that the real answer is that we need to implement a user
>preference page, so that the user can decide which (and when) the best
>values are for them.

I think there is a simpler solution: we should remember user's last
selection, the same we do with the selected columns. There is already an
issue for that for 1.7:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=6126
 

Cheers

Belén

>I will make sure this is captured as an enhancement request for 1.7 if it
>is not already.




>
>- David
>
>> -----Original Message-----
>> From: Lerner, Dave
>> Sent: Wednesday, April 09, 2014 10:28 AM
>> To: BARROS PENA, BELEN; Reyna, David
>> Cc: DAMIAN, ALEXANDRU
>> Subject: making recipes faster
>>
>> The simplest way to make recipes faster is to change the default row
>>count on
>> that page to 25 rows.  This will make the page show 4 times faster by
>>default
>> and still typically fill the browser with data.
>>
>> Can/should we do that (Even squeezing it in for the 1.6 release?)
>> -dave