[Gzz-commits] manuscripts/xupdf article.rst

[Janne V. Kujala]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Janne V. Kujala <address@hidden>        03/02/11 11:52:48

Modified files:
        xupdf          : article.rst 

Log message:
        compress impl

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

Patches:
Index: manuscripts/xupdf/article.rst
diff -u manuscripts/xupdf/article.rst:1.55 manuscripts/xupdf/article.rst:1.56
--- manuscripts/xupdf/article.rst:1.55  Tue Feb 11 10:50:53 2003
+++ manuscripts/xupdf/article.rst       Tue Feb 11 11:52:48 2003
@@ -476,47 +476,32 @@
 Implementation on the Gzz platform
 ==================================
 
-The implementation of the link structure and the above visual tenchiques
-is easy on the Gzz platform because of several features.
+The Gzz platform supports easy prototyping of the above link structure and 
+visual tenchiques because of several features.
 
-First, the Xanadu[XXX] structure implemented on Gzz 
-provides a way for specifying associations between parts
-of documents. Furthermore ...
-XXXidentity???
+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 
+for specifying associations between parts of documents. 
 
 Second, the Gzz view model provides a simple way of
 specifying geometry and automatic animation between views.
-
-A view, or a vobscene, contains coordinate systems and vobs.
-Vob is a "visual object" that knows how to draw itself using zero, 
-one, or more coordinate systems. For example, a text string 
-drawn starting at the unit square of a text coordinate system or
-a connection line drawn between the origins of two coordinate systems.
-The reason for separate coordinate systems is that a scene
-can be animated by interpolating the coordinate systems.
-
-The coordinate systems can be recursive so that one coordinate
-system is specified depending on another coordninate system.
-For example, the buoy coordinate system uses a transformation
-from the anchor position to the buoy position on a circle using
-the origin of the focus coordinate system.
-
-Each coordinate system has an identifier and a parent coordinate
-system. When the user moves from one view to another,
-the coordinate systems of the two vobscenes are matched.
-Matching coordinate systems (with matching parents) are smoothly 
-interpolated resulting in smooth animation from an object in one 
-scene to the corresponding object in the other scene.
-If an object only exists in one of the scenes, it appears or
-disappears at the middle point of the animation.
-
-Another important feature is the dynamic object model.
-Jython source files can be dynamically reloaded, and many 
-vobs can be specified simply as a string that is dynamically
-compiled to an OpenGL display list.
-Despite the dynamic nature, the code runs fast, because the 
+A view contains coordinate systems and vobs.
+Vob is a visual object that knows how to draw itself in
+one or more coordinate systems (for example, a connection line
+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.
+
+Third, most source code changes yield immediate effect without rebuilding.
+Jython source files can be dynamically reloaded and most vobs
+are specified using a string that is dynamically compiled into an 
+OpenGL display list.
+Despite this, the framerate is high, because the 
 interpolation of coordinate systems and the actual rendering of vobs 
-is performed by native C++ code.
+is finally performed by native C++ code.
 
 
 An example structure: a MEMEX-like view of recent hypertext and graphics 
articles