Patrick Ohly wrote:
We do get some information that can be used to provide at least some
feedback to the user whether the sync is almost done or will continue
to run for a while. I consider this useful information and would
like to show it. We just have to avoid the impression that this is in
any way a prediction of actual wall clock time, because any such
guess is very likely to be wrong (doesn't take size of items into
account, response times from server can vary a lot).
Yes, any progress bars or percentages will be more wrong than right
because of how syncml works, but they are still useful, giving some
sense of progress...
In particular the varying response times are the reason why I think
that the spinner should only spin while waiting for the server. It's
the indicator that all bets about deterministic completion times are
off, as in a web browser with a loaded server.
Does it really make sense that a spinner stops when we are processing
data? I would imagine web browsers show the spinner when rendering the
page takes a long time (but I don't actually know this).
Nick, comment?
- Jussi
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
