Patrick Ohly wrote:
On Tue, 2009-09-01 at 15:01 +0100, Jussi Kukkonen wrote:
Patrick Ohly wrote:
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).
No, they don't. I have a page which requires quite a bit of JavaScript
processing before displaying anything (a TiddlyWiki), and the spinner
stops several seconds before anything is drawn.
Ok, that probably settles it then... The bug is in my expectations not
in the spinner design ;)
We'll need to add something to the API, I guess. Status "running" could
be divided into "processing" and "waiting"?
- Jussi
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
