>From http://youtu.be/yIedljapuz0 (1:14)
QQQ
An interactive system's responsiveness is the most important factor in
determining *user satisfaction*.
Feedback is informing the user that actions were received and that the
software is now busy performing the task.
The main "time limits" for a response are:
- Button clicks: 0.1 sec.
- Drags: 0.1 sec.
- Long operations:
- A busy icon after about 1 second; a progress bar after about 3
seconds.
- Long operations should provide a cancel button.
Failure to meet these time limits frustrate and annoy users.
QQQ
This is a topic I've not consciously considered before. Nevertheless, Leo
does well here, with some (minor) deviations from the guidelines:
1. When loading lots of files, Leo displays progress in the log pane,
rather than with a progress indicator or cursor.
Imo, this is fine.
2. The recursive import command is one of Leo's most time-consuming
features. I've put a review of this command with regard to responsiveness
on the list. There used to be a bug where a dialog was brought up
repeatedly after creating lots of @auto nodes. I think this bug has been
fixed.
3. The make-sphinx button in LeoDocs.leo can take a long time. This is not
really a problem because the console displays the progress of Sphinx's make
command.
If anyone knows of serious violations of responsiveness, please let me know.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
