gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] manuscripts ./gzigzag.bib xupdf/article.rst


From: Tuomas J. Lukka
Subject: [Gzz-commits] manuscripts ./gzigzag.bib xupdf/article.rst
Date: Thu, 23 Jan 2003 07:15:51 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/01/23 07:15:51

Modified files:
        .              : gzigzag.bib 
        xupdf          : article.rst 

Log message:
        flowing

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/gzigzag.bib.diff?tr1=1.5&tr2=1.6&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/xupdf/article.rst.diff?tr1=1.16&tr2=1.17&r1=text&r2=text

Patches:
Index: manuscripts/gzigzag.bib
diff -u manuscripts/gzigzag.bib:1.5 manuscripts/gzigzag.bib:1.6
--- manuscripts/gzigzag.bib:1.5 Mon Jan 13 20:04:47 2003
+++ manuscripts/gzigzag.bib     Thu Jan 23 07:15:50 2003
@@ -357,6 +357,9 @@
  location = {Southampton, United Kingdom},
  doi = {http://doi.acm.org/10.1145/267437.267457},
  publisher = {ACM Press},
+ comment = {
+    Text of nodes is not shown, nodes shown as squares.
+ }
  }
 
 
Index: manuscripts/xupdf/article.rst
diff -u manuscripts/xupdf/article.rst:1.16 manuscripts/xupdf/article.rst:1.17
--- manuscripts/xupdf/article.rst:1.16  Thu Jan 23 06:23:34 2003
+++ manuscripts/xupdf/article.rst       Thu Jan 23 07:15:51 2003
@@ -40,6 +40,9 @@
 
     Spatial canvases might be nice but might be too much work.
 
+- What to call xupdf? We need some name for the view & structure demonstrated 
here.
+  Gzz is much more than this, but xupdf is not necessarily ideal ;)
+
 - why left-right, why not some other set of directions?
 
 Abstract
@@ -58,6 +61,11 @@
 Introduction
 ============
 
+Modern graphics accelerators enable, even on commodity hardware,
+several visual effects that were only possible 5 years ago on expensive
+graphics workstations. 
+It is time to re-examine the...
+
 In many hypertext systems today, following a link means a disruptive change
 in the user's workflow, replacing the current context with an
 entirely different one.
@@ -127,15 +135,15 @@
     -- 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.)
 
-- pad++ browser: shows linked docs next to it
-
 - Hypercept: [#milgram99hypercept]_
 
 
@@ -143,7 +151,7 @@
   transpointing windows [1979] are not about showing a set of links,
   but also represent connections crosscutting the view hierarchy.
   
-  Known implementations to date:
+  Known prototype implementations to date:
 
   - Southhampton transpointing windows demo
   - Nile
@@ -153,10 +161,11 @@
     existing view systems, but tricked its way around it)
 
 
-Modern graphics accelerators enable, even on commodity hardware,
-several visual effects that were only possible 5 years ago on expensive
-graphics workstations. 
-It is time to re-examine the...
+- pad++ browser: shows linked docs next to it
+
+
+In this article, we take the ideas seen in the above references
+a step further, by
 
 
 In this article, we ask what could be gained by using 




reply via email to

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