[Gzz-commits] manuscripts/UMLLink article.rst himalia-tour-be...

[Asko Soukka]

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

Modified files:
        UMLLink        : article.rst 
Added files:
        UMLLink        : himalia-tour-beginning.dia 
                         himalia-tour-returning.dia 

Log message:
        himalia strikes back

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/himalia-tour-beginning.dia?rev=1.1
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/himalia-tour-returning.dia?rev=1.1
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/article.rst.diff?tr1=1.101&tr2=1.102&r1=text&r2=text

Patches:
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.101 
manuscripts/UMLLink/article.rst:1.102
--- manuscripts/UMLLink/article.rst:1.101       Sat Feb 15 18:03:40 2003
+++ manuscripts/UMLLink/article.rst     Sat Feb 15 18:13:27 2003
@@ -9,7 +9,7 @@
 .. Alternative title: "Free Software toolchain for bidirectional 
    linking between UML diagrams and Javadoc"
 
-.. :Stamp: $Id: article.rst,v 1.101 2003/02/15 23:03:40 tuukkah Exp $
+.. :Stamp: $Id: article.rst,v 1.102 2003/02/15 23:13:27 humppake Exp $
 
 .. Points for HT people
    ====================
@@ -336,7 +336,7 @@
 The two types of documentation are complementary, as demonstrated 
 in Table [ref-documentations]:
 
-.. figure:: table
+.. figure:: __extended__
    :environment: table
    :label: documentations
    
@@ -455,7 +455,7 @@
 diagrams and implementation diagrams. Looking into the items available in
 each of these classes, we come to the conclusion shown in Table [ref-linking]_.
 
-.. figure:: table
+.. figure:: __extended__
    :environment: table
    :label: linking
    
@@ -884,7 +884,7 @@
 covers currently 26 different types of diagram items and is extended
 regularily as necessary.
 
-.. figure:: himalia-tour.gen.eps
+.. figure:: himalia-tour-beginning.gen.eps
    :environment: figure*
    :width: 15.7cm
    :label: screenshot
@@ -895,21 +895,42 @@
       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 "Frontend" documentation node. The diagram from the front 
-      page is 
-      implicitly included at the top of the page in small size.
+   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 "gzz.client" Javadoc package node. Several
+   c) Moved to "Space" Javadoc interface class node. A couple of
       implicitly embedded diagrams show the various contexts for 
       this package.
-   d) Moved to "PEG: Viewtool" documentation 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. "PEG" stands for "Proposals for Enchancing Gzz", and
-      it's a crucial part of our design documentation for future
-      improvements. 
+   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
+   :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. 
 
 Discussion
 ==========