102 |
In many hypertext systems today, following a link means a disruptive change |
In many hypertext systems today, following a link means a disruptive change |
103 |
in the user's workflow, replacing the current context with an |
in the user's workflow, replacing the current context with an |
104 |
entirely different one. |
entirely different one. |
105 |
This is possibly because most systems still use the paradigm developed in 70s |
The reason for this is that most systems still use the paradigm |
106 |
at Xerox PARC [XXXref] with |
(developed in 70s at Xerox PARC [XXXref]) of |
107 |
overlapping, rectangular, *independent* viewports to paper-like documents --- |
overlapping, rectangular, *independent* viewports to paper-like documents --- |
108 |
A link operation can only create a new window or switch the contents of an |
A link operation can only create a new window or switch the contents of an |
109 |
existing window. |
existing window. |
110 |
Alternatives, e.g., replacing part of text (XXX antont's reference) |
Alternatives, such as replacing part of text (XXX antont's reference), |
111 |
are not very popular and not so intuitive... [XXXref] |
are not very popular nor intuitive... [XXXref] |
112 |
|
|
113 |
There have been much work on improving user orientation. |
There have been much work on improving user orientation. |
114 |
One approach is to embed information about the destination in the links. |
One approach is to embed information about the destination in the links. |
115 |
Link titles are now a standard HTML feature (at least since 2.0) and |
Link titles are now a standard HTML feature (at least since version 2.0) and |
116 |
fluid links [zellweger98fluid]_ take the concept further by |
fluid links [zellweger98fluid]_ take the concept further by |
117 |
allowing a user to see gradually more and more target context |
allowing the user to see gradually more and more target context |
118 |
before following a link. |
before following a specific link. |
119 |
Hypercept [milgram99hypercept]_ provides a cue of local structure |
Hypercept [milgram99hypercept]_ provides a cue of local structure |
120 |
by animating the transition from current document to a linked |
by animating the transition from the current document to a linked |
121 |
document in different ways depending on the structural relationship |
document in different ways depending on the structural relationship |
122 |
exemplified by the link. |
exemplified by the link. |
123 |
|
|
124 |
.. XXX: behaviour, structural role |
.. XXX: behaviour, structural role |
125 |
|
|
126 |
Another approach is to show the context directly in the view layout. |
Another approach is to show the context directly in the view layout. |
127 |
Focus+context views of the web as proposed by Mukherjea and Hara |
Focus+context views of the web, as proposed by Mukherjea and Hara |
128 |
[mukharjea97fcwww]_ provide overview diagrams of the linking strucure |
[mukharjea97fcwww]_, provide overview diagrams of the linking strucure |
129 |
of web pages with important nodes emphasized. |
of web pages with important nodes emphasized. |
130 |
The Pad++ browser [fc-zooming]_ records history of the visited pages |
The Pad++ browser [fc-zooming]_ records history of the visited pages |
131 |
as a tree with nodes showing complete pages. |
as a tree with nodes showing complete pages. |
171 |
and local spatial structure is approximately maintained in transitions. |
and local spatial structure is approximately maintained in transitions. |
172 |
|
|
173 |
The interface requires less rigid structure of the view than |
The interface requires less rigid structure of the view than |
174 |
earlier interfaces. Only the relevant fragments of connected documents |
earlier interfaces. |
175 |
can be shown to be able to show all connected information. |
To be able to show all the connected information near the focus, |
176 |
|
only the relevant fragments of the linked documents can be shown. |
177 |
Therefore, we must be able to fluidly animate a fragment to |
Therefore, we must be able to fluidly animate a fragment to |
178 |
a whole document. |
a whole document. |
179 |
The new visual tecniques include buoys, link targets |
The new visual tecniques include link targets |
180 |
floating around the focus, break lines, a way of showing |
floating around the focus called *buoys*; *break lines*, a way of showing |
181 |
and animating a document fragment as a torn-off piece of the whole, |
and animating a document fragment as a torn-off piece of the whole; |
182 |
and unique background textures for visualising the identity |
and unique background textures for visualising the identity |
183 |
of the documents. |
of the documents. |
184 |
|
|
185 |
We present an example application that shows PDF documents |
We present an example application that shows PDF documents |
186 |
with connections and annotations using the new techniques. |
with connections and annotations using the new techniques. |
187 |
The application is based on xanalogical structure and, |
The application is based on a xanalogical structure and, |
188 |
orthogonal to it, on a spatial canvas structure that allows user to |
orthogonal to it, on a spatial canvas structure that allows the user to |
189 |
enter annotations and transclusions from the documents |
enter annotations and transclusions from the documents |
190 |
on a virtual canvas. Xanalogical links are allow the user |
on a virtual canvas. Xanalogical links allow the user |
191 |
to connect associated parts of documents. |
to connect associated parts of documents. |
192 |
|
|
193 |
|
|
197 |
.. In this article, we ask what could be gained by using |
.. In this article, we ask what could be gained by using |
198 |
|
|
199 |
|
|
200 |
In the following sections, ... |
In the following sections, we ... |
201 |
|
|
202 |
User-interface techniques enabled by fast hardware |
User-interface techniques enabled by fast hardware |
203 |
================================================== |
================================================== |
659 |
Acknowledgments |
Acknowledgments |
660 |
=============== |
=============== |
661 |
|
|
662 |
The authors would like to thank Tuukka Hastrup for discussions. |
The authors would like to thank Tuukka Hastrup and |
663 |
|
|
664 |
|
.. raw:: latex |
665 |
|
|
666 |
|
Hermanni Hyyti\"al\"a |
667 |
|
|
668 |
|
for discussions regarding this manuscript. |
669 |
|
|
670 |
.. bibliography:: gzigzag |
.. bibliography:: gzigzag |
671 |
|
|