[Gzz-commits] manuscripts UMLLink/umllink.rst xupdf/article.rst

[Tuomas J. Lukka]

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

Modified files:
        UMLLink        : umllink.rst 
        xupdf          : article.rst 

Log message:
        reorg

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

Patches:
Index: manuscripts/UMLLink/umllink.rst
diff -u manuscripts/UMLLink/umllink.rst:1.37 
manuscripts/UMLLink/umllink.rst:1.38
--- manuscripts/UMLLink/umllink.rst:1.37        Thu Jan 23 02:59:45 2003
+++ manuscripts/UMLLink/umllink.rst     Thu Jan 23 08:06:18 2003
@@ -2,8 +2,8 @@
 A free software toolchain for bidirectional linking between UML diagrams and 
Javadoc
 
====================================================================================
 
-:Stamp: $Id: umllink.rst,v 1.37 2003/01/23 07:59:45 tjl Exp $
-:Last-Modified: $Date: 2003/01/23 07:59:45 $
+:Stamp: $Id: umllink.rst,v 1.38 2003/01/23 13:06:18 tjl Exp $
+:Last-Modified: $Date: 2003/01/23 13:06:18 $
 
 Issues
 ======
@@ -345,43 +345,6 @@
  - small, incremental changes to existing javadoc / other documentation
 
  - Low threshold for writing new documentation, diagrams etc.
-
-reST's filosophy
-
- - indentation for blocks
- - robust for erros
- - "natural" to write
- - "ASCII layout" (our UML-language is an exception, which is discussed later)
-
-Why UML-language
-
- - minimum barrier to make a diagram (well, at first have to learn our 
UML-script)
-
- - separate UML structure from presentation, show structure in easily
-   editable text
-
- - direct manipulation when building diagrams clumsy
-
- - diagrams in the same reST source than the architecture document
-
- - only explicit link from diagram object to the class it represents is
-   obligatory, all other are implicit
-
-UML diagram component
-    
- - not strictly necessary; could have used another editor
-
- - problem: direct manipulation of UML diagrams very clunky
-
- - users are programmers --> allow a simple programming language
-
- - placement: currently metapost; looking at ways to make 
-   interactively editable.
-
-  + elements are easy to create by script language
-
-  + graphical placing could need an GUI
-
  - minimun barrier to drawing a even small diagram to make
    document more clear
 
@@ -474,6 +437,43 @@
  - outputs: easily adaptable to others (editing the source).
 
  - flow diagram of the implementation
+
+reST's filosophy
+
+ - indentation for blocks
+ - robust for erros
+ - "natural" to write
+ - "ASCII layout" (our UML-language is an exception, which is discussed later)
+
+Why UML-language
+
+ - minimum barrier to make a diagram (well, at first have to learn our 
UML-script)
+
+ - separate UML structure from presentation, show structure in easily
+   editable text
+
+ - direct manipulation when building diagrams clumsy
+
+ - diagrams in the same reST source than the architecture document
+
+ - only explicit link from diagram object to the class it represents is
+   obligatory, all other are implicit
+
+UML diagram component
+    
+ - not strictly necessary; could have used another editor
+
+ - problem: direct manipulation of UML diagrams very clunky
+
+ - users are programmers --> allow a simple programming language
+
+ - 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
 =============
Index: manuscripts/xupdf/article.rst
diff -u manuscripts/xupdf/article.rst:1.19 manuscripts/xupdf/article.rst:1.20
--- manuscripts/xupdf/article.rst:1.19  Thu Jan 23 07:33:07 2003
+++ manuscripts/xupdf/article.rst       Thu Jan 23 08:06:18 2003
@@ -279,13 +279,16 @@
 Vobs, coordsys, jython --> easy prototyping
 
 An example structure: a MEMEX-like view of recent hypertext and graphics 
articles
-===================================================================================================
+=================================================================================
 
 [#as-we-may-think] 
 
 
-Conclusions
-===========
+Conclusions and future work
+===========================
+
+There are several unresolved issues with the user interface 
+described here: