40 |
|
|
41 |
Spatial canvases might be nice but might be too much work. |
Spatial canvases might be nice but might be too much work. |
42 |
|
|
43 |
|
- What to call xupdf? We need some name for the view & structure demonstrated here. |
44 |
|
Gzz is much more than this, but xupdf is not necessarily ideal ;) |
45 |
|
|
46 |
- why left-right, why not some other set of directions? |
- why left-right, why not some other set of directions? |
47 |
|
|
48 |
Abstract |
Abstract |
61 |
Introduction |
Introduction |
62 |
============ |
============ |
63 |
|
|
64 |
|
Modern graphics accelerators enable, even on commodity hardware, |
65 |
|
several visual effects that were only possible 5 years ago on expensive |
66 |
|
graphics workstations. |
67 |
|
It is time to re-examine the... |
68 |
|
|
69 |
In many hypertext systems today, following a link means a disruptive change |
In many hypertext systems today, following a link means a disruptive change |
70 |
in the user's workflow, replacing the current context with an |
in the user's workflow, replacing the current context with an |
71 |
entirely different one. |
entirely different one. |
135 |
-- actually, not sure about stuff the user entered. |
-- actually, not sure about stuff the user entered. |
136 |
Certain about stuff the user circled/underlined/highlighted, though. |
Certain about stuff the user circled/underlined/highlighted, though. |
137 |
"Each annotation generates a query." |
"Each annotation generates a query." |
138 |
|
|
139 |
- Goal: "[A] modeless link *suggestion* mechanism" (emphasis mine). |
- Goal: "[A] modeless link *suggestion* mechanism" (emphasis mine). |
140 |
|
|
141 |
- Bad assumption in XLibris: "Although hypertext was designed |
- Bad assumption in XLibris: "Although hypertext was designed |
142 |
to address some of these problems [quickly jumping to related docs], |
to address some of these problems [quickly jumping to related docs], |
143 |
authors cannot anticipate the information needs of all readers." [schilit98digital] |
authors cannot anticipate the information needs of all readers." [schilit98digital] |
144 |
Therefore, *the readers must make the links*! (Or be able to.) |
Therefore, *the readers must make the links*! (Or be able to.) |
145 |
(Should be able to find this point somewhere.) |
(Should be able to find this point somewhere.) |
146 |
|
|
|
- pad++ browser: shows linked docs next to it |
|
|
|
|
147 |
- Hypercept: [#milgram99hypercept]_ |
- Hypercept: [#milgram99hypercept]_ |
148 |
|
|
149 |
|
|
151 |
transpointing windows [1979] are not about showing a set of links, |
transpointing windows [1979] are not about showing a set of links, |
152 |
but also represent connections crosscutting the view hierarchy. |
but also represent connections crosscutting the view hierarchy. |
153 |
|
|
154 |
Known implementations to date: |
Known prototype implementations to date: |
155 |
|
|
156 |
- Southhampton transpointing windows demo |
- Southhampton transpointing windows demo |
157 |
- Nile |
- Nile |
161 |
existing view systems, but tricked its way around it) |
existing view systems, but tricked its way around it) |
162 |
|
|
163 |
|
|
164 |
Modern graphics accelerators enable, even on commodity hardware, |
- pad++ browser: shows linked docs next to it |
165 |
several visual effects that were only possible 5 years ago on expensive |
|
166 |
graphics workstations. |
|
167 |
It is time to re-examine the... |
In this article, we take the ideas seen in the above references |
168 |
|
a step further, by |
169 |
|
|
170 |
|
|
171 |
In this article, we ask what could be gained by using |
In this article, we ask what could be gained by using |