[Gzz-commits] manuscripts/UMLLink article.rst

[Asko Soukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Asko Soukka <address@hidden>    03/02/15 18:27:11

Modified files:
        UMLLink        : article.rst 

Log message:
        himalia

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

Patches:
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.104 
manuscripts/UMLLink/article.rst:1.105
--- manuscripts/UMLLink/article.rst:1.104       Sat Feb 15 18:26:12 2003
+++ manuscripts/UMLLink/article.rst     Sat Feb 15 18:27:11 2003
@@ -9,7 +9,7 @@
 .. Alternative title: "Free Software toolchain for bidirectional 
    linking between UML diagrams and Javadoc"
 
-.. :Stamp: $Id: article.rst,v 1.104 2003/02/15 23:26:12 tuukkah Exp $
+.. :Stamp: $Id: article.rst,v 1.105 2003/02/15 23:27:11 humppake Exp $
 
 .. Points for HT people
    ====================
@@ -889,51 +889,51 @@
 
 .. figure:: himalia-tour-beginning.gen.eps
    :environment: figure*
-   :width: 15.7cm
+   :width: 15.6cm
    :label: screenshot
 
    A collage of screenshots from Gzz project documentation.
 
-       a) The front page of our design documentation. Items with blue
-          background act as links, the item in orange is the active document,
-          and "BROKEN LINK" marks that the item would be a link, but the 
-          target was unavailable.
-       b) Moved to "Backend" documentation node. The diagram from the front 
-          page is implicitly included at the top of the page in small size.
-          The item representing this node is marked with rough circling
-          in addition to orange background.
-       c) Moved to "Space" Javadoc interface class node. A couple of
-          implicitly embedded diagrams show the various contexts for 
-          this package.
-       d) Moved to "Cell" Javadoc class node. All diagrams are split 
-          in two by horizontal lines. Below a line is the diagram itself,
-          above is a list of the documentation nodes where the diagram is
-          explicitly included. Most of the diagrams in the current 
-          documentation is explitly included only once. The diagram in
-          this node is originally included in "Gzz Core APIs" documentation
-          node.
+   a) The front page of our design documentation. Items with blue
+      background act as links, the item in orange is the active document,
+      and "BROKEN LINK" marks that the item would be a link, but the 
+      target was unavailable.
+   b) Moved to "Backend" documentation node. The diagram from the front 
+      page is implicitly included at the top of the page in small size.
+      The item representing this node is marked with rough circling
+      in addition to orange background.
+   c) Moved to "Space" Javadoc interface class node. A couple of
+      implicitly embedded diagrams show the various contexts for 
+      this package.
+   d) Moved to "Cell" Javadoc class node. All diagrams are split 
+      in two by horizontal lines. Below a line is the diagram itself,
+      above is a list of the documentation nodes where the diagram is
+      explicitly included. Most of the diagrams in the current 
+      documentation is explitly included only once. The diagram in
+      this node is originally included in "Gzz Core APIs" documentation
+      node.
 
 .. figure:: himalia-tour-returning.gen.eps
    :environment: figure*
-   :width: 15.7cm
+   :width: 15.6cm
    :label: screenshot-2
 
    A collage of screenshots from Gzz project documentation.
   
-       a) Moved to "Gzz Core APIs" documentation node. The browser's 
-          viewport is scrolled to show the diagram. Diagrams included
-          explicitly are always full scaled.
-       b) Moved to the beginning of "Gzz Core APIs" documentation node.
-          Already famous diagram is shown implicitly embedded
-          at the top of the page in small size.
-       c) Moved to "Frontend" documentation node.
-       d) The journey ends to "gzz.client" Javadoc package node.
-          The rightmost of the implicitly embedded diagrams 
-          can be seen twice included explicitly in documentation.
-
-..  "PEG" stands for
-    "Proposals for Enchancing Gzz", and it's a crucial part of our
-    design documentation for future improvements. 
+   a) Moved to "Gzz Core APIs" documentation node. The browser's 
+      viewport is automaticly scrolled to show the diagram. 
+      Explicitly included diagrams are always shown full scaled.
+   b) Moved to the beginning of "Gzz Core APIs" documentation node.
+      Already famous diagram is shown implicitly embedded
+      at the top of the page in small size.
+   c) Moved to "Frontend" documentation node.
+   d) The journey ends to "gzz.client" Javadoc package node.
+      The rightmost of the implicitly embedded diagrams 
+      can be seen twice included explicitly in documentation. The
+      second explicit reference is done from node labeled
+      "PEG: ViewTool". "PEG" stands for "Proposals for Enchancing
+      Gzz", and it's a crucial part of our
+      design documentation for future improvements. 
 
 Discussion
 ==========