90 |
Introduction |
Introduction |
91 |
============ |
============ |
92 |
|
|
|
Modern graphics accelerators enable, even on commodity hardware, |
|
|
several visual effects that 5 years ago were only possible on expensive |
|
|
graphics workstations. |
|
|
It is time to re-examine the... |
|
|
|
|
93 |
In many hypertext systems today, following a link means a disruptive change |
In many hypertext systems today, following a link means a disruptive change |
94 |
in the user's workflow, replacing the current context with an |
in the user's workflow, replacing the current context with an |
95 |
entirely different one. |
entirely different one. |
96 |
|
This is possibly because most systems still use the paradigm developed in 70s |
97 |
|
at Xerox PARC [XXXref] with |
98 |
|
overlapping, rectangular, *independent* viewports to paper-like documents --- |
99 |
|
A link operation can only create a new window or switch the contents of an |
100 |
|
existing window. |
101 |
|
Alternatives, e.g., replacing part of text (XXX antont's reference) |
102 |
|
are not very popular and ... |
103 |
|
|
104 |
|
There have been various attempts to improve user orientation. |
105 |
|
One approach is to embed information about the destination |
106 |
|
or the link relationship in the links. |
107 |
|
Link titles are now a standard HTML feature (at least since 2.0) and |
108 |
|
fluid links [zellweger98fluid]_ take the concept further by |
109 |
|
allowing a user to see gradually more and more target context |
110 |
|
before following a link. |
111 |
|
Hypercept [milgram99hypercept]_ provides a cue of local structure |
112 |
|
by animating the transition from current document to a linked |
113 |
|
document in different ways depending on the structural relationship |
114 |
|
exemplified by the link. |
115 |
|
|
116 |
|
.. XXX: behaviour, structural role |
117 |
|
|
118 |
|
Another approach is to show the local structure directly in the view layout. |
119 |
|
Focus+context views of the web as proposed by Mukherjea and Hara |
120 |
|
[mukharjea97fcwww]_ provide overview diagrams of the linking strucure |
121 |
|
of web pages with important nodes emphasized. |
122 |
|
The Pad++ browser [fc-zooming]_ records history of the visited pages |
123 |
|
as a tree with nodes showing the complete pages. |
124 |
|
The focused page is shown at a larger scale and the user is free to |
125 |
|
pan and zoom the large virtual view with all layout changes |
126 |
|
fluidly animated. |
127 |
|
|
128 |
- possibly because most systems still use in the paradigm developed in 70s at Xerox PARC: |
.. - long pages get scrollbars |
|
|
|
|
- overlapping, rectangular, *independent* viewports to paper-like documents |
|
|
|
|
|
- link operation can only create new window or switch contents of window |
|
|
|
|
|
- alternatives, e.g. replacing part of text (XXX antont's reference) |
|
|
not very popular |
|
|
|
|
|
There have been various attempts to alleviate these problems: |
|
|
|
|
|
|
|
|
- `Link titles`_ (in the HTML standard at least since 2.0) |
|
|
give additional information by the linking page's author |
|
|
about a link's destination |
|
|
|
|
|
.. _Link titles: http://www.useit.com/alertbox/980111.html |
|
129 |
|
|
130 |
- Fluid links [zellweger98fluid]_ can be put in by the original author, |
Buoy-like annotation, less PARC-like: |
|
or by the user [XXX ht'01], |
|
131 |
|
|
132 |
- Fluid annotations can be rendered through a DOM: That is, |
In XLibris [XXX ht'02: going back in hypertext][schilit98digital]_, |
133 |
it suffices to modify the page's DOM and re-render, you don't |
recently visited pages are shown as thumbnails at the bottom of the window. |
134 |
have to turn the browser's rendering engine inside out to support |
Furthermore, |
|
lines cross-cutting the view hierarchy. This is why buoys would be |
|
|
harder to adopt into an existing program. The fluid stuff supports |
|
|
animation by modifying the DOM also (it simply grows a box). |
|
|
[XXX Hypermedia in the Small: Fluid annotations through |
|
|
open hypermedia: using and extending emerging web standards, WWW2002] |
|
|
|
|
|
- (IMHO) user interface problems: confuses using the mouse as eye or hand: |
|
|
normal mouse use: mouse = hand. quake mouse: mouse = eye. |
|
|
Here, neither paradigm applies fully as you would need to move both |
|
|
the mouse AND your eyes. |
|
|
|
|
|
- Also, the following the link that received the fluid annotation |
|
|
still has the same disruptive change. |
|
|
|
|
|
|
|
|
- Focus+context views of the web as proposed by |
|
|
Mukherjea and Hara [mukharjea97fcwww]_ give a 1'000ft |
|
|
view of the linking strucure (need to read & find out whether |
|
|
they show thumbnails, or what they show). |
|
|
Emphasis seems to be on the methods for generating the f+c structure, |
|
|
i.e., finding landmarks, paths between nodes, what nodes to show, etc. |
|
|
Some features used in the example views: |
|
|
|
|
|
- nodes are shown as cubes (focus node as a sphere) with titles |
|
|
- node size/height/color depicts importance/access frequency |
|
|
- landmark nodes distinguished by color |
|
|
- left/right direction for in/out links |
|
135 |
|
|
|
- In XLibris [XXX ht'02: going back in hypertext], recently visited |
|
|
pages are shown as thumbnails at the bottom of the window |
|
136 |
- Free form 'digital ink' annotation [e.g. XLibris, iMarkup?] is currently |
- Free form 'digital ink' annotation [e.g. XLibris, iMarkup?] is currently |
137 |
the closest thing to cross-cutting connections (because that's what |
the closest thing to cross-cutting connections (because that's what |
138 |
users do with them, at least sometimes) |
users do with them, at least sometimes) |
160 |
Therefore, *the readers must make the links*! (Or be able to.) |
Therefore, *the readers must make the links*! (Or be able to.) |
161 |
(Should be able to find this point somewhere.) |
(Should be able to find this point somewhere.) |
162 |
|
|
|
- Hypercept: [milgram99hypercept]_ |
|
163 |
|
|
164 |
- Nelson's as of yet unimplemented |
- Nelson's as of yet unimplemented |
165 |
transpointing windows [1979] are not about showing a set of links, |
transpointing windows [1979] are not about showing a set of links, |
175 |
existing view systems, but tricked its way around it) |
existing view systems, but tricked its way around it) |
176 |
|
|
177 |
|
|
|
- pad++ browser: shows linked docs next to it |
|
|
[fc-zooming]_ |
|
|
http://www.cs.umd.edu/hcil/pad++/papers/bookchap-98-webbrowser/index.html |
|
|
|
|
|
- builds a zoomable tree of the visited web pages |
|
|
- fluidly animates all view changes |
|
|
- page size proportional to the distance from focus |
|
|
- the layout depends on the order the user visits the pages |
|
|
- ancestor / descendant pages shown on left/right sides of a page |
|
|
- long pages get scrollbars |
|
|
|
|
178 |
In this article, we take the ideas seen in the above references |
In this article, we take the ideas seen in the above references |
179 |
a step further, by |
a step further, by |
180 |
|
|
186 |
we present some user interface technologies |
we present some user interface technologies |
187 |
developed for |
developed for |
188 |
|
|
189 |
|
Modern graphics accelerators enable, even on commodity hardware, |
190 |
|
several visual effects that 5 years ago were only possible on expensive |
191 |
|
graphics workstations. |
192 |
|
It is time to re-examine the... |
193 |
|
|
194 |
|
|
195 |
xupdf: |
xupdf: |
196 |
- less rigid structure of the view: |
- less rigid structure of the view: |
490 |
.. UML:: xupdfStructure |
.. UML:: xupdfStructure |
491 |
:caption: An UML diagram of the structure XXX. XXX orthogonal... |
:caption: An UML diagram of the structure XXX. XXX orthogonal... |
492 |
:width: 8cm |
:width: 8cm |
493 |
|
:alt: figuml |
494 |
|
|
495 |
class xuFluidMediaUnit |
class xuFluidMediaUnit |
496 |
fields |
fields |