Wow - I'm gonna check it out, it got the capabilities I was looking for, however it looks complex... guess it needs to be - as far as the "dot" language, that is... Hopefully it wont be to hard to set up an "org chart" looking view... since it's hierarchical.

Too bad there isn't something easier. I'm lazy in a good way(usually), and was really thinking of a template "explorer" not like the javascript click open deal, accepting the reload request delay from the server-side script, where I give each entry its own level - like html header tags, based on how deep into the structure, what "parent" it was under, what "children" and "link children" it had - or even a mock underlying directory structure with soft-links to mimic "links".

Maybe I've written my own enhancement request. I know it's a pretty specific application, but I'm just surprised that someone hasn't already done this. Maybe I'll also look into adapting the "familly tree" concept in greater detail before embarking on the GraphViz expedition.

Thanks... GraphViz looks pretty awesome, and if lazier routes fail, I'm sure to end up using it... and learning "dot"!

-Jeff

In reply to Re: Re: Dynamic FlowChart / Tree from KB relationship index by muad33b
in thread Dynamic FlowChart / Tree from KB relationship index by muad33b

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.