It's more aggressive in using the overall hierarchical tree structure of each page in showing/hiding: the reader can read (in increasing depth) page abstract, then by headers, then skim margin notes+item summaries, then read body text, then uncollapse regions to read those too.
-
-
RE: object permanence, I wonder if you could hit a middle-ground between this and
@gwern's hover-previews(nice for quick looks) by showing these expansions in a hover menu with a "pin" button, which when clicked, would insert the expansion into the document itself. -
The reader could then decide what parts they want to just preview, and which ones they want to keep around, actively participating in the structure of the document, but without contstant reflows of the main text as in the original prototype.
- 6 more replies
New conversation -
-
-
An important related consideration is "interaction considered harmful": ideally, the user should do as little as possible to access the ideal information. Lots of little buttons are a painful way to indicate intent; scrolling through thoughtful section hierarchy somewhat better.
-
"Saccade: The Ultimate UI" tl;dr: let's just give everyone VR HMDs with eyetracking and do everything based on saccades.
End of conversation
New conversation -
-
-
I think I would describe my experience of reading wikipedia as variable level of detail.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.