Refresh is "a state of mind", and this action could be between zero and Inf+. We should take a decision, split this distribution of times in two parts, what people think about a long-wait and not. 3 sec? 4 sec? more?
Local browsing, low number of files in a folder:
1. Joe open nautilus window and browse files...
2. Joe click on refresh button and all is good (less than 1 sec)
Local browsing, high number of files in a folder:
1. Joe open nautilus window for last year photos (around 1000)
2. Time step over 3 seconds, nautilus show a transient message with a stop button
3. Joe click stop
Network browsing for windirectories:
1. Joe open nautilus window and browse network dirs
2. Time step over 3 seconds, a new transient message with a stop button..
3. Joe don't click, transient message/window disappear after files come up
Refresh is "a state of mind", and this action could be between zero and Inf+. We should take a decision, split this distribution of times in two parts, what people think about a long-wait and not. 3 sec? 4 sec? more?
Local browsing, low number of files in a folder:
1. Joe open nautilus window and browse files...
2. Joe click on refresh button and all is good (less than 1 sec)
Local browsing, high number of files in a folder:
1. Joe open nautilus window for last year photos (around 1000)
2. Time step over 3 seconds, nautilus show a transient message with a stop button
3. Joe click stop
Network browsing for windirectories:
1. Joe open nautilus window and browse network dirs
2. Time step over 3 seconds, a new transient message with a stop button..
3. Joe don't click, transient message/window disappear after files come up