[Gzz-commits] gzz TODO

[Asko Soukka]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Asko Soukka <address@hidden>    03/01/13 08:40:12

Modified files:
        .              : TODO 

Log message:
        also TODO :)

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/TODO.diff?tr1=1.509&tr2=1.510&r1=text&r2=text

Patches:
Index: gzz/TODO
diff -u gzz/TODO:1.509 gzz/TODO:1.510
--- gzz/TODO:1.509      Mon Jan 13 04:11:27 2003
+++ gzz/TODO    Mon Jan 13 08:40:11 2003
@@ -161,10 +161,6 @@
           prototype of mindmap applitude (fall 2003?), check alternatives
        - umltool paper dl 15.2., but should actually be done in the late Jan
        - enhancing umltool
-           - important: add the explicit diagram references to the top edge
-             of the diagram!. 
-             If nothing else then at LEAST the location where it's defined 
ASAP.
-             The multi-ended link is otherwise working brilliantly.
            - write all errors and warnings in some place so it's easy to
              look for them and fix. Current output is incredibly bogously
              spewy.
@@ -172,32 +168,26 @@
              not there. For instance, gzz.DimManager is referenced but
              does not exist. Maybe show jlink in some special color
              (bright red?) if false.
-           - metapost directive: like .uml, but simply a metapost diagram.
-           - jlinks should also work in reverse: the UML diagram
-             should generate, for each jlink, a version of the diagram
-              with the jlink highlighted, and place that into the HTML
-             file that is being jlinked to.
-               - Currently diagrams are embedded into html-documents after
-                  the first header-tag. This could be enough for javadoc and
-                  other, but in reST this should be possible to overdrive by
-                  own directive.
-               - reST documents where diagram is explicitly included
-                  using the directive, should also be included into diagram
-                  (and highlighted when shown in current document)
-                - This requires really careful design. Maybe several
-                  implementation passes.
-                + Highlighting should be optional. This should be in UML 
source,
-                  but it could also be added there from an optin of UML 
directive.
-                  Anyway, implementing is not trivial, since even the same png
-                  diagram could be used in all documents, the imagemap should 
-                  always be regenerated. So, two points:
-                   - all refers to the same diagram should use the same png
-                   - still every document needs own imagemap
-                   - there should be no highlighting
+            - reST documents where diagram is explicitly included
+              using the directive, should also be included into diagram
+              (and highlighted when shown in current document)
+           - Currently diagrams are embedded into html-documents after
+              the first header-tag. This could be enough for javadoc and
+              other, but in reST this should be possible to overdrive by
+              own directive.
+           - better way to store setting, maybe distinct class
            - diagram names should be unique, currently this can't be
               easily tested, make something to it
            - Fix UML sequence diagram: now you have to put
              seqobjects *after* the sequence...
+            + Highlighting should be optional. This should be in UML source,
+              but it could also be added there from an optin of UML directive.
+              Anyway, implementing is not trivial, since even the same png
+              diagram could be used in all documents, the imagemap should 
+              always be regenerated. So, two points:
+                   - all refers to the same diagram should use the same png
+                   - still every document needs own imagemap
+                   - there should be no highlighting
        - split this todo into correct releases / sections :)
        - write about representing mind map in ZZ
            - how different dimensions would be used