1 |
|
- `Link titles`_ (in the HTML standard at least since 2.0) |
2 |
|
give additional information by the linking page's author |
3 |
|
about a link's destination |
4 |
|
|
5 |
|
.. _Link titles: http://www.useit.com/alertbox/980111.html |
6 |
|
|
7 |
|
- Fluid links [zellweger98fluid]_ can be put in by the original author, |
8 |
|
or by the user [XXX ht'01], |
9 |
|
|
10 |
|
- Fluid annotations can be rendered through a DOM: That is, |
11 |
|
it suffices to modify the page's DOM and re-render, you don't |
12 |
|
have to turn the browser's rendering engine inside out to support |
13 |
|
lines cross-cutting the view hierarchy. This is why buoys would be |
14 |
|
harder to adopt into an existing program. The fluid stuff supports |
15 |
|
animation by modifying the DOM also (it simply grows a box). |
16 |
|
[XXX Hypermedia in the Small: Fluid annotations through |
17 |
|
open hypermedia: using and extending emerging web standards, WWW2002] |
18 |
|
|
19 |
|
- (IMHO) user interface problems: confuses using the mouse as eye or hand: |
20 |
|
normal mouse use: mouse = hand. quake mouse: mouse = eye. |
21 |
|
Here, neither paradigm applies fully as you would need to move both |
22 |
|
the mouse AND your eyes. |
23 |
|
|
24 |
|
- Also, the following the link that received the fluid annotation |
25 |
|
still has the same disruptive change. |
26 |
|
|
27 |
|
|
28 |
|
- Focus+context views of the web as proposed by |
29 |
|
Mukherjea and Hara [mukharjea97fcwww]_ give a 1'000ft |
30 |
|
view of the linking strucure (need to read & find out whether |
31 |
|
they show thumbnails, or what they show). |
32 |
|
Emphasis seems to be on the methods for generating the f+c structure, |
33 |
|
i.e., finding landmarks, paths between nodes, what nodes to show, etc. |
34 |
|
Some features used in the example views: |
35 |
|
|
36 |
|
- nodes are shown as cubes (focus node as a sphere) with titles |
37 |
|
- node size/height/color depicts importance/access frequency |
38 |
|
- landmark nodes distinguished by color |
39 |
|
- left/right direction for in/out links |
40 |
|
|
41 |
|
- In XLibris [XXX ht'02: going back in hypertext], recently visited |
42 |
|
pages are shown as thumbnails at the bottom of the window |
43 |
|
- Free form 'digital ink' annotation [e.g. XLibris, iMarkup?] is currently |
44 |
|
the closest thing to cross-cutting connections (because that's what |
45 |
|
users do with them, at least sometimes) |
46 |
|
|
47 |
|
- Point to make: This form of annotation (buoy-like) is nothing new... |
48 |
|
Maybe start with 'old fashioned ink annotation' and then introduce |
49 |
|
forms of representing linking in computers? |
50 |
|
|
51 |
|
- also used a lot for images, see the NASA example image |
52 |
|
in irregu |
53 |
|
|
54 |
|
- XLibris [schilit98digital]_ also automatically searches for pages |
55 |
|
matching stuff the user entered/circled on a page, and place |
56 |
|
a thumbnail in the margin -> linking with visible targets |
57 |
|
(no automatic placing as with buoys, though) |
58 |
|
-- actually, not sure about stuff the user entered. |
59 |
|
Certain about stuff the user circled/underlined/highlighted, though. |
60 |
|
"Each annotation generates a query." |
61 |
|
|
62 |
|
- Goal: "[A] modeless link *suggestion* mechanism" (emphasis mine). |
63 |
|
|
64 |
|
- Bad assumption in XLibris: "Although hypertext was designed |
65 |
|
to address some of these problems [quickly jumping to related docs], |
66 |
|
authors cannot anticipate the information needs of all readers." [schilit98d |
67 |
|
igital]_ |
68 |
|
Therefore, *the readers must make the links*! (Or be able to.) |
69 |
|
(Should be able to find this point somewhere.) |
70 |
|
|
71 |
|
- Hypercept: [milgram99hypercept]_ |
72 |
|
|
73 |
|
- Nelson's as of yet unimplemented |
74 |
|
transpointing windows [1979] are not about showing a set of links, |
75 |
|
but also represent connections crosscutting the view hierarchy. |
76 |
|
|
77 |
|
Known prototype implementations to date: |
78 |
|
|
79 |
|
- Southhampton transpointing windows demo |
80 |
|
- Nile |
81 |
|
- Cosmicbook? (Has anybody tried this?) |
82 |
|
- seems to be vapourware |
83 |
|
- To some degree, Pyxi (which didn't solve the problem with the |
84 |
|
existing view systems, but tricked its way around it) |
85 |
|
|
86 |
|
|
87 |
|
- pad++ browser: shows linked docs next to it |
88 |
|
[fc-zooming]_ |
89 |
|
http://www.cs.umd.edu/hcil/pad++/papers/bookchap-98-webbrowser/index.html |
90 |
|
|
91 |
|
- builds a zoomable tree of the visited web pages |
92 |
|
- fluidly animates all view changes |
93 |
|
- page size proportional to the distance from focus |
94 |
|
- the layout depends on the order the user visits the pages |
95 |
|
- ancestor / descendant pages shown on left/right sides of a page |
96 |
|
- long pages get scrollbars |
97 |
|
|
98 |
|
|
99 |
|
|
100 |
|
|
101 |
|
|
102 |
|
|
103 |
.. UML:: zzStructure |
.. UML:: zzStructure |
104 |
|
|
105 |
class zzSpace |
class zzSpace |