Difference between revisions of "Wgraph:Requests for new features"

Revision as of 05:24, 25 July 2007

lomg description.

As far as I see there are some inconsistencies within aiSee, which should be repaired.

Gero 15:02, 21 July 2007 (CEST)

A 'backrange' property and a 'backclass' property would be nice. They would allow to traverse edges in reverse order. It should be possible to specify these properties in addition to 'class' and 'range'.

Similarly it should be possible to specify only target nodes and classes and/or backclasses; aiSee would have to look for the source nodes which lead to the specified target nodes.

Gero 15:01, 21 July 2007 (CEST)

Wgraph could save its result as a normal wiki image in the hashed directory tree. Is this really desirable?
Can we avoid to update the image if the wgraph statement does not change between two edits?
Currently thumb, png and svg are always produced. We could save resources because not all variants are always needed.
make example 3 prettier
improve and document commandline interface of #wgraph
cross-check with aiSee reference manual, refer to commands/properties described there
reproduce subgraph exsample no.8 of aiSee manual
check 'level', 'layer', 'vertical_order' and document the behaviour
can UML sequence state charts easily be drawn? Are levels helpful?
document inputbox extension
link Examples among each other
improve Wgraph manual
use generic nodetype '*' for attributes which are assigned to all nodes
use generic edgetype '*' for attributes which are assigned to all edges
make another example where namespaces (category, template, main) are mapped to nodetypes

@@ Line 43: / Line 43: @@
 * use generic nodetype '*' for attributes which are assigned to all nodes
 * use generic edgetype '*' for attributes which are assigned to all edges
+* make another example where namespaces (category, template, main) are mapped to nodetypes