232 |
To be able to show all the link targets near the focus, |
To be able to show all the link targets near the focus, |
233 |
only the *relevant fragments* (the immediate surroundings of the other |
only the *relevant fragments* (the immediate surroundings of the other |
234 |
end of the link) of the target nodes can be shown. |
end of the link) of the target nodes can be shown. |
235 |
|
The images of the link targets should "float" relatively near the anchors, |
236 |
|
which is why we call them *buoys*. |
237 |
|
|
238 |
In order to make this work from a user interface perspective, |
Fragments of different documents can look very similar, |
239 |
we need to be able to help the user recognize the target documents, |
especially preattentively ("at-a-glance"). |
240 |
since document fragments can be confusing. |
In order to let the user perceive the source of the fragment, |
241 |
|
we texture each node with a k |
242 |
|
|
243 |
|
In order to show the user which node a given fragment belongs, |
244 |
|
there are some obvious alternatives: do nothing, or show the node title. |
245 |
|
We have developed another |
246 |
|
3) show a unique background texture. |
247 |
|
In order to save screen estate, |
248 |
|
we have chosen the third alternative. |
249 |
|
|
250 |
|
|
251 |
Therefore, we must be able to fluidly animate a fragment to |
Therefore, we must be able to fluidly animate a fragment to |