[Gzz-commits] manuscripts/UMLLink umllink.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/01/23 08:33:35

Modified files:
        UMLLink        : umllink.rst 

Log message:
        structuring

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

Patches:
Index: manuscripts/UMLLink/umllink.rst
diff -u manuscripts/UMLLink/umllink.rst:1.40 
manuscripts/UMLLink/umllink.rst:1.41
--- manuscripts/UMLLink/umllink.rst:1.40        Thu Jan 23 08:28:47 2003
+++ manuscripts/UMLLink/umllink.rst     Thu Jan 23 08:33:35 2003
@@ -2,8 +2,8 @@
 A free software toolchain for bidirectional linking between UML diagrams and 
Javadoc
 
====================================================================================
 
-:Stamp: $Id: umllink.rst,v 1.40 2003/01/23 13:28:47 tjl Exp $
-:Last-Modified: $Date: 2003/01/23 13:28:47 $
+:Stamp: $Id: umllink.rst,v 1.41 2003/01/23 13:33:35 tjl Exp $
+:Last-Modified: $Date: 2003/01/23 13:33:35 $
 
 Issues
 ======
@@ -350,6 +350,9 @@
 After Step 1 from user's perspective, the computer has *all* the information
 needed for steps 2 and 3, so *no further changes should be required*.
 
+ - only explicit link from diagram object to the class it represents is
+   obligatory, all other are implicit
+
 For Step 1, it is best to demand explicit links in the UML diagrams.
 
 Steps 2,3:
@@ -361,7 +364,8 @@
 
 Goals:
 
- - "feeling" that the arch. doc will be read(!)
+ - "feeling" that the arch. doc will be read because
+   of the backlinks(!)
 
  - if diagrams try to link objects, which don't exist (e.g. removed
    Java class), the linking objects will be specially marked 
@@ -382,7 +386,7 @@
 documents they relate to. They function like navigation bars on the 
 WWW, except that the same page may have several of them.
 
- - make diagrams work as context+focusing menus to the code documentation
+- make diagrams work as context+focusing menus to the code documentation
 
 - Borges's "taxonomy" for animals;
   http://www.multicians.org/thvv/borges-animals.html
@@ -460,32 +464,28 @@
 
 Why UML-language
 
- - minimum barrier to make a diagram (well, at first have to learn our 
UML-script)
+ - not strictly necessary; could have used another editor
 
- - separate UML structure from presentation, show structure in easily
-   editable text
+ - minimum barrier to make a diagram (well, at first have to learn our 
UML-script)
 
- - direct manipulation when building diagrams clumsy
+ - direct manipulation when building / editing structure of diagrams clumsy
+ 
+     - users are programmers --> a simple programming language is better than 
d.m.
 
- - diagrams in the same reST source than the architecture document
+      + elements are easy to create by script language
 
- - only explicit link from diagram object to the class it represents is
-   obligatory, all other are implicit
+      + graphical placing could need an GUI
 
-UML diagram component
-    
- - not strictly necessary; could have used another editor
+ - diagrams in the same reST source as the architecture document
 
- - problem: direct manipulation of UML diagrams very clunky
+ - separate UML structure from presentation, show structure in easily
+   editable text
 
- - users are programmers --> allow a simple programming language
+     - placement: currently metapost; looking at ways to make 
+       interactively editable.
 
- - placement: currently metapost; looking at ways to make 
-   interactively editable.
 
-  + elements are easy to create by script language
 
-  + graphical placing could need an GUI
 
 
 Practical use