/[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.79 by jvk, Thu Feb 13 12:50:52 2003 UTC revision 1.80 by jvk, Thu Feb 13 13:39:30 2003 UTC
# Line 213  Distortion-oriented Focus+Context view o Line 213  Distortion-oriented Focus+Context view o
213    
214  Distortion-oriented Focus+Context views are already well-known  Distortion-oriented Focus+Context views are already well-known
215  [fc-fisheye]_ XXXmorerefs.  [fc-fisheye]_ XXXmorerefs.
216  We use a continuous fisheye distortion as a focus on large documents.  We use a continuous fisheye distortion as a focus of large documents.
217  The magnification and size of the focus is user-adjustable and  The magnification and size of the focus is user-adjustable and
218  it can me moved independent of the focus (node) in the connection structure.  it can me moved independent of the focus (node) in the connection structure.
219    
# Line 247  We use buoys as link targets floating ar Line 247  We use buoys as link targets floating ar
247  For the layout of the buoys, several desirable layout constraints  For the layout of the buoys, several desirable layout constraints
248  can be enumerated:  can be enumerated:
249    
250      - buoys should not be placed directly on the focus  - buoys should not be placed directly on the focus
251    - buoys should be placed close to their anchors
252      - buoys should be placed close to their anchors  - buoys anchored closer to the focus should be larger
253    - the view should animate continuously when the focus moves
     - buoys anchored closer to the focus should be larger  
   
     - the layout should animate continuously when the focus moves  
254    
255  Furthermore,  Furthermore,
256  It is important to maintain orientation locally (i.e., left/right  It is important to maintain orientation locally,
257  direction of links, etc.) but the space need not be globally  that is, going in one direction should result in arriving from
 euclidian. This matches the way the brain understands space  
 as globally distorted, segmented, locally Euclidian views.  
 Some refs (should search for more/better):  
 http://acad88.sahs.uth.tmc.edu/research/publications/iccs2001spatial.pdf  
 [wang01mindsviews]_  
 http://citeseer.nj.nec.com/hunt99orientation.html  
   
 That is, going in one direction should result in arriving from  
258  the opposite direction, so that the local spatial structure  the opposite direction, so that the local spatial structure
259  does not change too much.  does not change too much.
260    This matches the way the brain understands space
261    as globally distorted, segmented, locally Euclidian views
262    (see, e.g. [wang01mindsviews]_).
263    
264    .. http://acad88.sahs.uth.tmc.edu/research/publications/iccs2001spatial.pdf
265    .. http://citeseer.nj.nec.com/hunt99orientation.html
266    
267  Because of this, each link has a specific left-right orientation  Because of this, each link has a specific left-right orientation
268  so that a right-end buoy is drawn on the right side of the view  so that a right-end buoy is drawn on the right side of the view
269  and a left-end buoy on the left side.  and a left-end buoy on the left side.
270    
271  More than two opposing directions could also be used, but  More than two opposing directions could also be used, but
272    is is not required for the local spatial coherence and it would also
273          - it is not required for maintaining the sense of direction  limit the layout of a large number of buoys.
274    Furthermore, there is usually no meaningful global 2D layout for
275          - it would limit the layout of a large number of buoys  a network of nodes, so the extra directions would not help much
276    in perceiving the position in the global structure.
277          - there is usually no meaningful global 2D layout of a network  In our application, the structure has simply directed links,
278            of nodes; in our application, the structure has simply  visualized as the left-right direction of the connection lines.
279            directed links, visualized as the left-right direction.  
280    As for the horizontal orientation of the link direction,
281  The horizontal orientation is more natural than, e.g., vertial, because  it is more natural than vertial,
282  the visual field is wider than it is tall  because the visual field is wider than it is tall
283  (as exemplified by the usual screen aspect ratios of 4:3 and 16:9)  (as exemplified by the usual screen aspect ratios of 4:3 and 16:9)
284  leaving more space at the left and right sides than on the top and bottom.  leaving more space at the left and right sides than on the top and bottom.
285  XXX: left and right hand???  XXX: left and right hand???
# Line 321  We choose the geometry as follows: Line 316  We choose the geometry as follows:
316    
317     \begin{figure}     \begin{figure}
318     \centering     \centering
319     \includegraphics[width=8cm]{buoyGeometry}     \includegraphics[width=8.45cm]{buoyGeometry}
320     \caption{     \caption{
321     \label{figbuoygeom}     \label{figbuoygeom}
322     Buoy layout geometry: XXX}       Buoy layout geometry: XXX}  
# Line 469  The Gzz platform supports easy prototypi Line 464  The Gzz platform supports easy prototypi
464  visual tenchiques because of several features.  visual tenchiques because of several features.
465    
466  First, the Gzz storage model (Storm[XXX]) provides globally unique  First, the Gzz storage model (Storm[XXX]) provides globally unique
467  identities [lukka02guids]_ for the documents and structural nodes and  identities [lukka02guids-andalso-mealling-leach-salz02-uuidnamespace]_
468    for the documents and structural nodes and
469  the xanalogical[XXX] structure implemented on Gzz is a convenient way  the xanalogical[XXX] structure implemented on Gzz is a convenient way
470  for specifying associations between parts of documents.  for specifying associations between parts of documents.
471    
# Line 501  An example structure: a MEMEX-like view Line 497  An example structure: a MEMEX-like view
497    
498  ..  UML:: xupdfStructure  ..  UML:: xupdfStructure
499      :caption: An UML diagram of the structure XXX. XXX orthogonal...      :caption: An UML diagram of the structure XXX. XXX orthogonal...
500      :width: 8cm      :width: 8.45cm
501      :alt: figuml      :alt: figuml
502    
503      class xuFluidMediaUnit      class xuFluidMediaUnit
# Line 639  Conclusions and future work Line 635  Conclusions and future work
635    
636  - We have presented many tecniques...  - We have presented many tecniques...
637    
638    - More than sum of its parts
639    
640  - Similar techniques have been used in static diagrams;  - Similar techniques have been used in static diagrams;
641    we have added the continuous animation.    we have added the continuous animation.
642    

Legend:
Removed from v.1.79  
changed lines
  Added in v.1.80

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