Ohhh. Hardly enough said. (01)
It is very interesting to have the graphviz tools.
And there is much more that I would like to see happen with it. (02)
But mostly, I would like to have the graph visualization tools
and wiki tools joined together. (03)
Specifically. I wish that I could say something like: (04)
digraph MyWikiConcept { (05)
MyWikiConcept -> MyOtherWikiConcept;
MyWikiConcept -> [Your Wiki Concept];
[Your Wiki Concept] -> AnOtherWikiConcept (label = alternative);
} (06)
And have this in a wiki word (as text)
And have that then display a graph using the graphviz tools
and then have each of the identified nodes link to wiki
words. (07)
Right now, I have to do it as images. And it is hard to manage. (08)
For example, in my networking class, I used the following diagrams: (09)
digraph route {
routing -> "routing protocols";
routing -> "routing issues";
"routing issues" -> "route aggregation";
"routing issues"-> "autonomous system number";
"routing issues" -> "router discovery";
"routing issues" -> "routing policy";
"router discovery"-> "ICMP";
"router discovery" -> "router solicitation";
"router discovery" -> "router advertisment"; (010)
routing -> "routing problems" -> "routing loops";
"routing problems" -> "routing loops"; (011)
"routing issues" -> "route filtering";
"routing problems" -> "count to infinity problem";
"routing problems" -> "route flapping"; (012)
"routing protocols" -> "static route";
"routing protocols" -> "distance vector" -> "rip";
"routing protocols" -> "link state" -> "OSPF";
"routing protocols" -> "path vector" -> "BGP"; (013)
} (014)
digraph routing-protocols {
"distance vector" -> "hop count";
"routing protocols" -> "IS-IS"; (015)
"link state" -> "Cost of service";
"link state" -> "performance";
"link state" -> "most secure path";
"routing protocols" -> "static route";
"routing protocols" -> "distance vector" -> "rip";
"routing protocols" -> "link state" -> "OSPF";
"routing protocols" -> "path vector" -> "BGP";
"routing protocols" -> "IGP" -> "Internal Gateway protocol";
"routing protocols" -> "EGP" -> "External Gateway protocol"; (016)
"rip" -> "rip1";
"rip" -> "rip2";
"rip1" -> "rip1 vs rip2";
"rip2" -> "rip1 vs rip2" ; (017)
"rip1 vs rip2" -> "route mask propogation";
"rip1 vs rip2" -> "non local route propogation";
"rip1 vs rip2" -> "Non-rip updates" ;
"rip1 vs rip2" -> "route tags"; (018)
} (019)
digraph OSPF {
OSPF ->"LSA";
OSPF -> "hello";
OSPF -> "neighbors";
OSPF -> "flooding";
OSPF -> "synchronization";
OSPF -> "designated router";
OSPF -> "backup designated router";
OSPF -> "OSPF area";
} (020)
digraph routing-daemons { (021)
routing -> "route daemons" -> "gated" -> OSPF;
gated -> rip;
gated -> BGP;
gated -> "gated.conf";
"route daemons" -> "routed" -> rip;
"route daemons" -> "zebra"; (022)
} (023)
It leads quickly to getting control of concepts maps. (024)
this is different than the dynamic mapping that you are doing with
TouchGraph, because I want to be explicit about the links
that are shown in the page directly. (025)
And yet, I want it group editable. (026)
Jack Park <jackpark@thinkalong.com> writes: (027)
% http://c2.com/cgi/wiki?GraphViz
%
% Take a look. Enough said.
% Jack
%
% ---------------------------------------------------------------------------
% XML Topic Maps: Creating and Using Topic Maps for the Web.
% Addison-Wesley. Jack Park, Editor. Sam Hunting, Technical Editor
%
% Build smarter kids globally to reduce the need for smarter bombs.
%
%
% --
% This message is archived at:
%
%
http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=tools-yak&i=5.1.1.6.0.20030417091705.04acacc0@thinkalong.com (028)
-----
John Sechrest . Helping people use
CTO PEAK - . computers and the Internet
Public Electronic . more effectively
Access to Knowledge,Inc .
1600 SW Western, Suite 180 . Internet: sechrest@peak.org
Corvallis Oregon 97333 . (541) 754-7325
. http://www.peak.org/~sechrest (029)
--
This message is archived at: (030)
http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=tools-yak&i=200304171626.h3HGQRL27328@jas.peak.org (031)
|