[Gzz-commits] journals humppake

[Asko Soukka]

CVSROOT:        /cvsroot/fenfire
Module name:    journals
Changes by:     Asko Soukka <address@hidden>    03/05/27 03:57:17

Modified files:
        .              : humppake 

Log message:
        twid

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/journals/humppake.diff?tr1=1.46&tr2=1.47&r1=text&r2=text

Patches:
Index: journals/humppake
diff -u journals/humppake:1.46 journals/humppake:1.47
--- journals/humppake:1.46      Mon May 26 09:56:08 2003
+++ journals/humppake   Tue May 27 03:57:17 2003
@@ -1,30 +1,74 @@
-Uncheckduled:
-    - Back to WheelViews, tests
-    - Back to MindMap applitude
+==============
+Asko's journal
+==============
 
-2003-05-29 -> 2003-06-01 Ascension Day, Sowing vacation (HL)
+Working generally Mon-Fri and 40h/week till 17.9.2003.
+Most usual working time is 1000-1800GMT+2 +/- 2 hours.
+Lunch hours are embedded.
+
+----
+Loom
+----
+
+    - is pin like stub good enough
+    - reimplementing other views from GZZ
+      + can WheelView be good enough for general Navigation
+      + how about row and column views showing structure deeper
+    - optimize WheelViews to human made structure
+      + how human made RDF should be presented in general
+      + how to preserve spatiality of the structure
+      + how RDF could be shown as spatial space like ZZ
+    - WheelViews to use scaled Vobs/NodeViews
+
+-------
+MindMap
+-------
+    - View (for what) or PP like applitude
+    - Using of buoyoing? papers? textures?
+    - Compromises between spatial 2D mindmaps and easily
+      traversable nD structure
+    - literature review of mindmaps and note taking in general
+
+-------
+Navidoc
+-------
+
+    - robust interface to handle several config.py:s
+    - releasing 0.1
+      + stripping all extra (too Fenfire depended) stuff
+    - documenting
+      + usage
+      + redocumenting code
+      + [navidoc] document docutils.conf:datestamp -additions (CVS_DATE,
+        CVS_VERSION, SSI_LASTMOD) somewhere
+      + documenting UML syntax
+    - can something be unit tested? test
+    - clarifying error messages
+    - parser more robust
+    - parser to work with fixed UML syntax
+    - fixing UML syntax for 0.1
+
+---------
+Scheduled
+---------
+
+2003-05-29 -> 2003-06-01 Ascension Day, Sowing vacation (KL), Weekend
 
 2003-05-31
-    - [navidoc] syntax to follow Fenfire coding standards
-    - [navidoc] documenting, tests
-    - [navidoc] document docutils.conf:datestamp -additions (CVS_DATE,
-      CVS_VERSION, SSI_LASTMOD) somewhere
     - submit short article about Navidoc
-    - verify links in existing diagrams.
-    - [benja] make javadoc generation recursive: instead
-      of listing all packages in DOCPKGS, do the inverse
-      and list only the *excluded* ones
 
 2003-05-23
     - Navidoc short paper ready for proofreading
     - create tests for Jython encoding problem
 
-.. ps. Working generally Mon-Fri and 40h/week. Most usual working time 
-       is 1000-1800GMT+2 +/- 2 hours. Lunch hours are embedded.
-
-============
+------------
 Past:
-============
+------------
+
+2003-05-27
+   - [benja] make javadoc generation recursive: instead
+     of listing all packages in DOCPKGS, do the inverse
+     and list only the *excluded* ones
 
 2003-05-26 (7 1/2h)
    - fixing dep directive in Navidoc UML