[Gzz-commits] manuscripts/UMLLink short-paper.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/05/21 04:52:40

Modified files:
        UMLLink        : short-paper.rst 

Log message:
        spatialmenus

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/short-paper.rst.diff?tr1=1.19&tr2=1.20&r1=text&r2=text

Patches:
Index: manuscripts/UMLLink/short-paper.rst
diff -u manuscripts/UMLLink/short-paper.rst:1.19 
manuscripts/UMLLink/short-paper.rst:1.20
--- manuscripts/UMLLink/short-paper.rst:1.19    Wed May 21 04:44:17 2003
+++ manuscripts/UMLLink/short-paper.rst Wed May 21 04:52:40 2003
@@ -2,7 +2,7 @@
 Bridging Javadoc and design documentation via UML diagram image maps
 ====================================================================
 
-.. $Id: short-paper.rst,v 1.19 2003/05/21 08:44:17 tjl Exp $
+.. $Id: short-paper.rst,v 1.20 2003/05/21 08:52:40 tjl Exp $
 
 .. short paper == 2 pages, deadline the end of May
 
@@ -175,10 +175,15 @@
 the documents for the different program elements 
 is attractive exactly because of this: each diagram
 in which an element appears gives some of the necessary
-context for that element. Inserting copies of each UML diagram
-in which a given class appears to its Javadoc as an imagemap
-for jumping to the other related classes
-is a good
+context for that element. 
+Since the diagrams also appear on the design documentation,
+which is definitely related to the program elements
+described in the diagram, it should also be reachable
+through the spatial menu in the diagram --- we insert
+elements showing the location where the diagram appears
+in the design documentation into the diagrams as well.
+Figure XXX shows some example HTML pages produced by our system.
+
 
 ..  Because UML diagrams should be made anyway, it is good start to
     think about using them also for navigation.