[Gzz-commits] manuscripts/UMLLink article.rst

[Asko Soukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Asko Soukka <address@hidden>    03/02/13 04:40:34

Modified files:
        UMLLink        : article.rst 

Log message:
        twid

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

Patches:
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.13 
manuscripts/UMLLink/article.rst:1.14
--- manuscripts/UMLLink/article.rst:1.13        Thu Feb 13 04:39:45 2003
+++ manuscripts/UMLLink/article.rst     Thu Feb 13 04:40:34 2003
@@ -5,7 +5,7 @@
 .. Alternative title: "Free Software toolchain for bidirectional 
    linking between UML diagrams and Javadoc"
 
-.. :Stamp: $Id: article.rst,v 1.13 2003/02/13 09:39:45 humppake Exp $
+.. :Stamp: $Id: article.rst,v 1.14 2003/02/13 09:40:34 humppake Exp $
 
 .. Points for HT people
    ====================
@@ -311,19 +311,6 @@
      replacing already created object
 
 
- - How should we discuss WYSIWYG, WYSIAYG/WYSIATI for reST &c? Someone will
-   surely ask about that,
-
-    PARTIAL RESOLUTION: 
-
-       - proprietarity (really?)
-       - versioning much worse 
-          (changes in rtf could probably be compared?)
-       - users = programmers --> used to editing text and compiling,
-          it's the most practical to use the same editor as for coding
-       - lack of good, **extensible** tools
-
-
 Docutils
 --------
 
@@ -335,6 +322,20 @@
 - "ASCII layout" (our language for UML is an exception, which is discussed 
   later)
 
+can generate useless diagrams from the code class hierarchy 
+     * should describe somewhere why these are useles... 
+     * uses proprietary GraphViz tool to create diagrams
+ - How should we discuss WYSIWYG, WYSIAYG/WYSIATI for reST &c? Someone will
+   surely ask about that,
+
+    PARTIAL RESOLUTION: 
+
+       - proprietarity (really?)
+       - versioning much worse 
+          (changes in rtf could probably be compared?)
+       - users = programmers --> used to editing text and compiling,
+          it's the most practical to use the same editor as for coding
+       - lack of good, **extensible** tools
   
    [gentner-nielsen96anti-mac, p.75] collects arguments/argues
    generally against WYSIWYG.