[Gzz-commits] manuscripts/UMLLink article.rst

[Tuukka Hastrup]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuukka Hastrup <address@hidden> 03/02/15 16:47:41

Modified files:
        UMLLink        : article.rst 

Log message:
        screenshot caption rewording

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

Patches:
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.90 
manuscripts/UMLLink/article.rst:1.91
--- manuscripts/UMLLink/article.rst:1.90        Sat Feb 15 16:16:18 2003
+++ manuscripts/UMLLink/article.rst     Sat Feb 15 16:47:41 2003
@@ -9,7 +9,7 @@
 .. Alternative title: "Free Software toolchain for bidirectional 
    linking between UML diagrams and Javadoc"
 
-.. :Stamp: $Id: article.rst,v 1.90 2003/02/15 21:16:18 humppake Exp $
+.. :Stamp: $Id: article.rst,v 1.91 2003/02/15 21:47:41 tuukkah Exp $
 
 .. Points for HT people
    ====================
@@ -120,7 +120,7 @@
 them by hand is tedious and error-prone when they are authored using different
 software. 
 
-In this article, we present a navigational aid for software engineering 
documentation.
+In this article, we present a navigational aid for software documentation.
 Based on using UML diagrams as multi-ended links, our tool connects two
 distinct areas of software engineering documentation: 
 the general architectural documents and the detailed method-level javadoc 
documentation.
@@ -887,21 +887,24 @@
 
    A collage of screenshots from Gzz project documentation.
 
-   a) The "frontpage" of our design documentation. Objects with blue
-      background are linked, the item describing the active document
-      is marked with orange background and "BROKEN LINK" marks that 
-      element is defined to be linked,but the target couldn't be found.
-   b) Moved to "Frontend". The implicitly embedded diagram from the
-      front page is included at the top of the page as 50% diminished
-      version. The element representing active document page "Frontend" is
-      in addition to orange background, also rounded with rough edge.
-   c) Moved to "gzz.client" Javadoc package description page. Several
-      implicitly embedded diagrams shows the package's context. 
-   d) Moved to "PEG: Viewtool". All diagrams are split in two by
-      horizontal line. Below the line is the diagram itself. Above is
-      listed the documentation pages, where the diagram is explicitly
-      included. "PEG" stands for "Proposals for Enchancing Gzz" and
-      it's crucial part of our design documentation for future
+   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 "Frontend" 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
+      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. 
 
 Discussion