[Gzz-commits] gzz/Documentation/Presentations/ThursdaySeminar...

[Asko Soukka]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Asko Soukka <address@hidden>    03/03/26 09:31:28

Modified files:
        Documentation/Presentations/ThursdaySeminar03: ABSTRACTS 

Log message:
        some

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS.diff?tr1=1.8&tr2=1.9&r1=text&r2=text

Patches:
Index: gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS
diff -u gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS:1.8 
gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS:1.9
--- gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS:1.8     Wed Mar 
26 04:36:05 2003
+++ gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS Wed Mar 26 
09:31:28 2003
@@ -100,8 +100,6 @@
 
 ..  (and other aids for our software development)
 
-..  generally about these by-products
-
     Navidoc is a collection of lightweight tools built to support our
     project's documentation. Navidoc expands UML diagrams embedded in
     design documentation to work as multi-ended links, which 
@@ -109,10 +107,32 @@
     documentation. For describing UML diagrams, Navidoc provides a 
     readily-authored lexical language, which can be written within 
     design documentation. The example of Navidoc enhanced documentation 
-    couldbe found at http://himalia.it.jyu.fi/gzzdoc/
+    could be found at http://himalia.it.jyu.fi/gzzdoc/
 
-..  test system (moving towerds XP, meaning of unit test in it, 
-    tools for lowering the  threshold of writing test)
+..  - developed as byproduct
+      * components/features added when needed
+    - Navidoc
+      * linking different documentations via UML diagrams
+       + design documentation
+       + javadoc
+       + lexically described UML diagrams within design documentation
+       + postprocessing html files, adding imagemaps and images,
+          creating crosslinks/backlinks
+      * Gzz's documentation in himalia as example
+    - built especially to fit for our needs, to fit and support
+      our software development process
+      * usable with any text editor
+      * use of open software toolchain
+    - using reStructuredText
+      * documentation and code could be written with same tools
+      * "language" could be expanded with directives
+      * describing diagrams lexically within documentation
+      * describing diagrams is easy, placing could be difficult
+      * (pegboard)
+      * (latex writer)
+    - test framework
+      * adopting XP, importance of writing tests
+      * framework minimizes the gap of writing and running test
 
 Vesa Kaihlavirta