[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] manuscripts/xupdf article.rst
From: |
Tuomas J. Lukka |
Subject: |
[Gzz-commits] manuscripts/xupdf article.rst |
Date: |
Fri, 14 Feb 2003 07:04:57 -0500 |
CVSROOT: /cvsroot/gzz
Module name: manuscripts
Changes by: Tuomas J. Lukka <address@hidden> 03/02/14 07:04:56
Modified files:
xupdf : article.rst
Log message:
Reorging
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/xupdf/article.rst.diff?tr1=1.94&tr2=1.95&r1=text&r2=text
Patches:
Index: manuscripts/xupdf/article.rst
diff -u manuscripts/xupdf/article.rst:1.94 manuscripts/xupdf/article.rst:1.95
--- manuscripts/xupdf/article.rst:1.94 Fri Feb 14 04:53:52 2003
+++ manuscripts/xupdf/article.rst Fri Feb 14 07:04:56 2003
@@ -86,11 +86,10 @@
upon traversing
a link, the view fluidly animates to the target, while the
originating document remains visible.
-We use directed but bidirectional links to retain the left-right
-relationships between nodes.
We have developed new user interface techniques
-to facilitate this interface, which together:
+to facilitate this type of interface, which are especially
+effective when used in combination.
- break lines: the buoy is actually a torn-off piece of the whole other end of
the link!
@@ -103,6 +102,9 @@
fragments of the linked-to documents (called buoys)
floating near the anchors in the article..
+We use directed but bidirectional links to retain the left-right
+relationships between nodes.
+
The individual nodes use fisheye
The user interface techniques have been made possible
@@ -115,7 +117,7 @@
Introduction
============
-In many hypertext systems today, following a link means a disruptive change
+In several hypertext systems today, following a link means a disruptive change
in the user's workflow, replacing the current context with an
entirely different one.
The reason for this is that most systems still use the paradigm
@@ -125,13 +127,16 @@
existing window.
Alternatives, such as replacing part of text (XXX antont's reference),
are not very popular nor intuitive... [XXXref]
+Improving user orientation through user interface improvements has
+recently received much attention.
-There have been much work on improving user orientation.
-One approach is to embed information about the destination in the links.
-Link titles are now a standard HTML feature (at least since version 2.0) and
-fluid links [zellweger98fluid]_ take the concept further by
+One approach is to display information about the destinations of the links.
+Browsers' status lines or tooltips show the URL or the HTML link title of the
link
+that the mouse is currently over.
+Fluid links [zellweger98fluid]_ take the concept further by
allowing the user to see gradually more and more target context
before following a specific link.
+
Hypercept [milgram99hypercept]_ provides a cue of local structure
by animating the transition from the current document to a linked
document in different ways depending on the structural relationship
@@ -139,10 +144,13 @@
.. XXX: behaviour, structural role
-Another approach is to show the context directly in the view layout.
+Another approach is to treat the local hypertext structure as a graph,
+and visualize it as such.
Focus+context views of the web, as proposed by Mukherjea and Hara
-[mukharjea97fcwww]_, provide overview diagrams of the linking strucure
+[mukharjea97fcwww]_ and Munzner and Burchard[fc-3dhyperbolic]_,
+provide overview diagrams of the linking strucure
of web pages with important nodes emphasized.
+
The Pad++ browser [fc-zooming]_ records history of the visited pages
as a tree with nodes showing complete pages.
The focused page is shown at a larger scale and the user can
@@ -151,34 +159,23 @@
.. - long pages get scrollbars
-While focus+context views of the linking relationships provide good overview,
-the interconnections of documents are deeper.
-Nelson's as of yet unimplemented transpointing windows [XXXref 1979]
+Nelson's transpointing windows [XXXref 1979]
show connections crosscutting the view hierarchy
between relevant parts of documents.
This form of annotation is often used on images:
a label is placed on the margin and a line is drawn to the relevant
-point in the image.
+point in the image. XXX See fig.XXX
Free form 'digital ink' annotation
(e.g., XLibris [schilit98digital]_, iMarkup[XXref])
-is currently the closest thing to cross-cutting connections,
-because that's what users do with them.
-However, document authors cannot anticipate the information
-needs of all readers, so the user also needs a way to make
-connections between multiple documents.
-XLibris automatically searches for pages containing contant similar
+allow cross-cutting connections inside a single document.
+The XLibris system also
+searches for pages containing contant similar
to what the user underlined or circled on a page,
and suggests links to the related pages as thumbnails in the margin.
-
In this article, we take the ideas seen in the above references
-a step further.
-Modern graphics accelerators enable, even on commodity hardware,
-several visual effects that 5 years ago were only possible on expensive
-graphics workstations.
-We present a number of user interface technologies that are now possible
-on typical hardware.
+a logical step further.
These techniques together make it possible to implement a
new focus+context user interface with two important features.
First, all connected information is visible in fine detail
@@ -197,6 +194,13 @@
and animating a document fragment as a torn-off piece of the whole;
and unique background textures for visualising the identity
of the documents.
+
+Modern graphics accelerators enable, even on commodity hardware,
+several visual effects that 5 years ago were only possible on expensive
+graphics workstations.
+We present a number of user interface technologies that are now possible
+on typical hardware.
+
We present an example application that shows PDF documents
with connections and annotations using the new techniques.
- [Gzz-commits] manuscripts/xupdf article.rst, (continued)
- [Gzz-commits] manuscripts/xupdf article.rst, Janne V. Kujala, 2003/02/13
- [Gzz-commits] manuscripts/xupdf article.rst, Janne V. Kujala, 2003/02/13
- [Gzz-commits] manuscripts/xupdf article.rst, Matti Katila, 2003/02/13
- [Gzz-commits] manuscripts/xupdf article.rst, Matti Katila, 2003/02/13
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/13
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/13
- [Gzz-commits] manuscripts/xupdf article.rst, Matti Katila, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Matti Katila, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Matti Katila, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Matti Katila, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst,
Tuomas J. Lukka <=
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Benja Fallenstein, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/14
- [Gzz-commits] manuscripts/xupdf article.rst, Tuomas J. Lukka, 2003/02/14