Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I try to design applications to be robust in the face of accidents -- either slips (inadvertent operations, such as clicking in the wrong place) or mistakes (cognitive errors, such as clicking Ok vs. Cancel on a dialog). Some ways to do this are:</p> <ol> <li>infinite (or at least multi-step) undo / redo</li> <li>integrate documentation with the interface, via dynamic tooltips and other context-sensitive means of communication (One paper that is particularly relevant is about <a href="http://loki.lokislabs.org/weblog/archives/2003/09/17/surpriseexplainreward.php" rel="noreferrer">'Surprise, Explain, Reward'</a> (direct link: <a href="ftp://ftp.cs.orst.edu/pub/burnett/chi03.curiosity.pdf" rel="noreferrer">SER</a>) -- using typical psychological responses to unexpected behavior to inform users)</li> <li>Incorporate the state of the system into said documentation (use the current user's data as examples, and make the documentation concrete by using data that they can see <em>right now</em>)</li> <li><em>Expect</em> user error. If there's a chance that someone will try to write to a:\ when there isn't a disk in place, then implement a time-out so the system can fail gracefully, and prompt for another location. Save the data in memory until it's secure on disk, etc.</li> </ol> <p>This boils down to two core things: (1) Program defensively, and (2) Keep the user as well informed as you can. If the system's interface is easy to use, and behaves according to their expectations then they are more likely to <em>know</em> which button to click when an annoying dialog appears.</p> <p>I also try very, very hard to avoid anything modal, so users <em>can</em> ignore most dialogs I have to use, at least for a while (and when they really need to pay attention to them, they have enough information to know what to do with it).</p> <p>It's impossible to make a system completely fool-proof, but I've found that the above techniques go a long way in the right direction. (and they have been incorporated in the systems used to develop Surprise Explain Reward and other tools that have been vetted by extensive user studies.)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow would you handle users who don't read dialog boxes?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USrcreswick
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow would you handle users who don't read dialog boxes?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAbsolutely agree with the undo/redo suggestion. Missing (or worse, partial) undo support is one of the worst and most common UI mistakes.
      singulars
      1. PO
      1. USmarijne
    2. COExcellent answer, Ctrl+D
      singulars
      1. PO
      1. USJonas Gulle
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload