gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/xupdf article.rst


From: Janne V. Kujala
Subject: [Gzz-commits] manuscripts/xupdf article.rst
Date: Thu, 13 Feb 2003 03:33:56 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Janne V. Kujala <address@hidden>        03/02/13 03:33:56

Modified files:
        xupdf          : article.rst 

Log message:
        more intro

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/xupdf/article.rst.diff?tr1=1.70&tr2=1.71&r1=text&r2=text

Patches:
Index: manuscripts/xupdf/article.rst
diff -u manuscripts/xupdf/article.rst:1.70 manuscripts/xupdf/article.rst:1.71
--- manuscripts/xupdf/article.rst:1.70  Wed Feb 12 19:17:16 2003
+++ manuscripts/xupdf/article.rst       Thu Feb 13 03:33:56 2003
@@ -99,11 +99,10 @@
 A link operation can only create a new window or switch the contents of an
 existing window.
 Alternatives, e.g., replacing part of text (XXX antont's reference)
-are not very popular and ...
+are not very popular and not so intuitive... [XXXref]
 
-There have been various attempts to improve user orientation.
-One approach is to embed information about the destination
-or the link relationship in the links.
+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 2.0) and
 fluid links [zellweger98fluid]_ take the concept further by
 allowing a user to see gradually more and more target context 
@@ -115,73 +114,51 @@
 
 .. XXX: behaviour, structural role
 
-Another approach is to show the local structure directly in the view layout.
+Another approach is to show the context directly in the view layout.
 Focus+context views of the web as proposed by Mukherjea and Hara 
 [mukharjea97fcwww]_ 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 the complete pages.
+as a tree with nodes showing complete pages.
 The focused page is shown at a larger scale and the user is free to
 pan and zoom the large virtual view with all layout changes
 fluidly animated.
 
 ..  - long pages get scrollbars
 
-Buoy-like annotation, less PARC-like:
+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] 
+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.
+
+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 similar
+content the user underlined or circled on a page, 
+and suggests links to the related pages as thumbnails in the margin.
 
-- In XLibris [XXX ht'02: going back in hypertext][schilit98digital]_, 
-  recently visited pages are shown as thumbnails at the bottom of the window.
-  Furthermore,
-
-- Free form 'digital ink' annotation [e.g. XLibris, iMarkup?] is currently
-  the closest thing to cross-cutting connections (because that's what
-  users do with them, at least sometimes)
-
-  - Point to make: This form of annotation (buoy-like) is nothing new...
-    Maybe start with 'old fashioned ink annotation' and then introduce
-    forms of representing linking in computers?
-
-       - also used a lot for images, see the NASA example image
-         in irregu
-
-  - XLibris [schilit98digital]_ also automatically searches for pages
-    matching stuff the user entered/circled on a page, and place
-    a thumbnail in the margin -> linking with visible targets
-    (no automatic placing as with buoys, though)
-    -- actually, not sure about stuff the user entered.
-    Certain about stuff the user circled/underlined/highlighted, though.
-    "Each annotation generates a query."
-
-  - Goal: "[A] modeless link *suggestion* mechanism" (emphasis mine).
-
-  - Bad assumption in XLibris: "Although hypertext was designed
-    to address some of these problems [quickly jumping to related docs],
-    authors cannot anticipate the information needs of all readers." 
[schilit98digital]_
-    Therefore, *the readers must make the links*! (Or be able to.)
-    (Should be able to find this point somewhere.)
-
-
-- Nelson's as of yet unimplemented
-  transpointing windows [XXXref 1979] are not about showing a set of links,
-  but also represent connections crosscutting the view hierarchy.
-  
-  Known prototype implementations to date:
-
-  - Southhampton transpointing windows demo
-  - Nile
-  - Cosmicbook?  (Has anybody tried this?)
-    - seems to be vapourware
-  - To some degree, Pyxi (which didn't solve the problem with the
-    existing view systems, but tricked its way around it)
 
+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. 
 It is time to re-examine the...
 
-In this article, we take the ideas seen in the above references
-a step further. 
+we present some user interface technologies 
+developed for 
+
+These tecniques together enable
 
 We present a focus+context user interface, that 
 
@@ -195,8 +172,6 @@
        - parts of documents shown
        - layout changes
 
-we present some user interface technologies 
-developed for 
 
 additional cues for identity and context:
 
@@ -206,8 +181,9 @@
        - fisheye
        - nadir
 
-These tecniques together 
-
+Mention user editability
+.. Therefore, *the readers must make the links*! (Or be able to.)
+.. (Should be able to find this point somewhere.)
 
 .. In this article, we ask what could be gained by using 
 
@@ -465,12 +441,12 @@
 Implementation on the Gzz platform
 ==================================
 
-The Gzz platform supports easy prototyping of the above link structure and 
+The Gzz platform supports easy prototyping of the above structural and 
 visual tenchiques because of several features.
 
 First, the Gzz storage model (Storm[XXX]) provides globally unique
 identities for the documents and structural nodes and
-the Xanadu[XXX] structure implemented on Gzz is a convenient way 
+the xanalogical[XXX] structure implemented on Gzz is a convenient way 
 for specifying associations between parts of documents. 
 
 Second, the Gzz view model provides a simple way of
@@ -481,8 +457,8 @@
 vob draws a line between the origins of two coordinate systems). 
 When the user moves from one view to another,
 the coordinate systems of the first view are 
-interpolated to the matching coordinate systems of the
-following scene, resulting in smooth animation.
+interpolated to the corresponding coordinate systems of the
+following view, resulting in smooth animation.
 
 Third, most source code changes yield immediate effect without rebuilding.
 Jython source files can be dynamically reloaded and most vobs




reply via email to

[Prev in Thread] Current Thread [Next in Thread]