/[gzz]/manuscripts/xupdf/article.rst
ViewVC logotype

Diff of /manuscripts/xupdf/article.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.135 by jvk, Sat Feb 15 15:58:40 2003 UTC revision 1.136 by jvk, Sat Feb 15 18:54:19 2003 UTC
# Line 712  techniques in a user interface for brows Line 712  techniques in a user interface for brows
712  a combined spatial and xanalogical hypertext structure.  a combined spatial and xanalogical hypertext structure.
713  The idea is to allow the user to create a structure for browsing,  The idea is to allow the user to create a structure for browsing,
714  annotating and connecting  annotating and connecting
715  PDF files (e.g. academic articles) obtained from other sources.  PDF files (e.g., academic articles) obtained from other sources.
716    
717  We take Cells a la Nelson's ZigZag[XXX ref] to be fundamental, point-like nodes  We take Cells a la Nelson's ZigZag[XXX ref] to be fundamental, point-like nodes
718  of the structure. A cell can have two types of relationships, as shown  of the structure. A cell can have two types of relationships, as shown
# Line 731  the original and the copy, and our user Line 731  the original and the copy, and our user
731  the xanalogically connected cells' contexts as buoys.  the xanalogically connected cells' contexts as buoys.
732    
733  The xanalogical structure also allows for explicit xu Links, which are simply  The xanalogical structure also allows for explicit xu Links, which are simply
734  associations between two enfilades. These are also shown as buoys.  associations between two *enfilades* (lists of references to fluid media units).
735    
736  The PDF files obtained from external sources are considered to be images  .. These are also shown as buoys.
 from the xanalogical media perspective.  
 In addition to showing the canvases and the cells on them, the primary  
 application: browsing PDF files suggests allowing the user to also browse  
 whole PDF scrollblocks.  
   
 the view should show in the buoys the important structure, i.e.,  
   
         - pdf-image-blocks should be shown as buoys anchored  
           at the other end of xu-link or at a transclusion show on screen  
         - the blocks for user-entered annotations should not be  
           shown but instead the canvases containing them  
737    
738  (note: the same holds for the identity for bg textures).  .. XXX: permanent vs fluid media
739       *fluid media* should be shortly defined
740    
741  the canvas structure can easily be extended to support "digital ink"  The PDF files obtained from external sources fit in the xanalogical structure
742  annotations  as fluid media image blocks,
743    and the content of the annotations made by the user are stored in
744    fluid media text blocks.
745    In addition to showing the canvases and the cells on them, the primary
746    application, browsing PDF files, suggests allowing the user to also browse
747    whole PDF image blocks.
748    When browsing a PDF image block, the relevant fragments of xanalogically
749    linked documents and canvases containing a transclusion of the current document
750    are shown as buoys.
751    
752    An important point here is that the user interface
753    only shows the structure that is relevant from the user's point of view.
754    A canvas node shows the original PDFs transcluded in the canvas as buoys,
755    but the user is not interested in seeing the constituent media blocks of the annotations.
756    For the same reason the annotations on a canvas do not have unique background textures
757    (as the PDF transclusions do), but the whole canvas has a unique background texture
758    based on its identity.
759    
760    The left-right orientation of the xanalogically linked buoys is determined by
761    the direction of the xanalogical link.
762    In this prototype, the orientation of a transclusion is fixed so
763    that a transcluding canvas is always left of the PDF image block.
764    
765  .. raw:: latex  .. raw:: latex
766    
# Line 787  described here: Line 798  described here:
798    
799          -          -
800    
801    the canvas structure can easily be extended to support "digital ink"
802    annotations
803    
804    
805  The idea of making nodes recognizable so when coming  The idea of making nodes recognizable so when coming
806  across a familiar node through an unfamiliar route, it would  across a familiar node through an unfamiliar route, it would
807  be immediately recognizable.  be immediately recognizable.

Legend:
Removed from v.1.135  
changed lines
  Added in v.1.136

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26