Re: [graphviz-interest] Dendrograms/Cladograms
Pander <[email protected]> Mon, 28 Dec 2015 12:43:41 +0100
| Newsgroups | gmane.comp.video.graphviz |
|---|---|
| Message-ID | <[email protected]> |
--===============6109899484697617978== Content-Type: multipart/alternative; boundary="----GYUH81625AYLCJTV9FKWIYRLDQRD96" Content-Transfer-Encoding: 7bit ------GYUH81625AYLCJTV9FKWIYRLDQRD96 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Nice to see this being discussed and helped forward. If this is new compa= red to the already exists demos, please add it there. For sure more peopl= e might be interested and can find a nice showcase with wich they immedia= tely can get started.=20 On 27 December 2015 22:22:45 CET, Ron Savage <[email protected]> wrote: >Hi Hermann > >On 27/12/15 22:09, [email protected] wrote: >> Hi Ron, >> >> the ASCII layouts do not look nice for me. >> But thanks to the given URLs I modified them ([1],[2]). > >Thanx for the effort. I see you've vertically aligned the names. It=20 >looks good, but I fear there has been a misunderstanding. > >The ASCII diagrams were just to help me perfect the user-friendly file=20 >format I designed so both people preparing such files find them easy,=20 >and I find it easy to parse such files. Here again are the *.clad >files: > >Parent Place Node >root above Beetles >root below 1 >1 above Wasps, bees, ants >1 below 2 >2 above Butterflies, moths >2 below Flies > >Parent Place Node >root above Archaeopterix lithographica >root below 1 >1 above Apsaravis ukhaana >1 below 2 >2 above Gansus yumemensis >2 below 3 >3 above Ichthyornis dispar >3 below 4 >4 above 5 >4 below 6 >5 above Gallus gallus >5 below Anas clypeata >6 above Pasquiaornis >6 below 7 >7 above Enaliornis >7 below 8 >8 above Baptornis advenus >8 below 9 >9 above 10 >9 below 11 >10 above Brodavis varnei >10 below Brodavis baileyi >11 above Fumicollis hoffmani >11 below 12 >12 above Parahesperornis alexi >12 below Hesperornis regalis > >As for the JSON, I would never impose on my users the requirement of=20 >having to type in something like that. I do admit the JSON is easier to > >get right than YAML, but since we're talking about something a human >has=20 >to type, my one-and-only concern is ease of use. > >It's only after a program has parsed such data that the programmer can=20 >produce versions of the file in various formats. > >And yes, I do use JSON, but only where I can call a library module (in=20 >Perl) from one of my CGI scripts (also in Perl, based on Mojolicious),=20 >to turn a data structure into JSON so when that data is sent to the web > >client (typically a browser [*]), the data structure can be easily=20 >decoded by Javascript. > >[*] Just for the record, some web clients are not browsers. In fact=20 >millions of them are not browsers. > >I have finished the parser, and almost finished the whole program.=20 >Progress is here: > >http://savage.net.au/misc/wikipedia.01.png > >http://savage.net.au/misc/nationalgeographic.01.png > >Ignore the fuschia boxes. They are just inserted to make it easy for me > >to deal with the remaining problem of overlapping text. > >As you can see, I've figured out how to shift the text when it >overlaps,=20 >but I have not yet shifted the corresponding connecting lines. Hey! >It's=20 >only 8:17 am here now. I'll update the images during the day. > >And the scaffolding nodes, whose names are digits, will obviously be=20 >suppressed later. > >The output you see is generated purely by default options within the=20 >program. There are almost a dozen options so far. All the user has to >do=20 >is provide the *.clad files above. Simple! > >--=20 >Ron Savage - savage.net.au >_______________________________________________ >[email protected] >http://lists.research.att.com/mailman/listinfo/graphviz-interest ------GYUH81625AYLCJTV9FKWIYRLDQRD96 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head></head><body>Nice to see this being discussed and helped forw= ard. If this is new compared to the already exists demos, please add it t= here. For sure more people might be interested and can find a nice showca= se with wich they immediately can get started. <br><br><div class=3D"gmai= l_quote">On 27 December 2015 22:22:45 CET, Ron Savage <[email protected].= au> wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0= pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <pre class=3D"k9mail">Hi Hermann<br /><br />On 27/12/15 22:09, hermann@st= amm-wilbrandt.de wrote:<br /><blockquote class=3D"gmail_quote" style=3D"m= argin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1= ex;"> Hi Ron,<br /><br /> the ASCII layouts do not look nice for me.<br /= > But thanks to the given URLs I modified them ([1],[2]).<br /></blockquo= te><br />Thanx for the effort. I see you've vertically aligned the names.= It <br />looks good, but I fear there has been a misunderstanding.<br />= <br />The ASCII diagrams were just to help me perfect the user-friendly f= ile <br />format I designed so both people preparing such files find them= easy, <br />and I find it easy to parse such files. Here again are the *= .clad files:<br /><br />Parent Place Node<br />root above Beetles<br />ro= ot below 1<br />1 above Wasps, bees, ants<br />1 below 2<br />2 above = Butterflies, moths<br />2 below Flies<br /><br />Parent Place Node<br />= root above Archaeopterix lithographica<br />root below 1<br />1 above Apsaravis ukhaana<br />1 below 2<br />2 above Gansus yu= memensis<br />2 below 3<br />3 above Ichthyornis dispar<br />3 below 4= <br />4 above 5<br />4 below 6<br />5 above Gallus gallus<br />5 belo= w Anas clypeata<br />6 above Pasquiaornis<br />6 below 7<br />7 above = Enaliornis<br />7 below 8<br />8 above Baptornis advenus<br />8 below = 9<br />9 above 10<br />9 below 11<br />10 above Brodavis varnei<br />1= 0 below Brodavis baileyi<br />11 above Fumicollis hoffmani<br />11 bel= ow 12<br />12 above Parahesperornis alexi<br />12 below Hesperornis reg= alis<br /><br />As for the JSON, I would never impose on my users the req= uirement of <br />having to type in something like that. I do admit the J= SON is easier to <br />get right than YAML, but since we're talking about= something a human has <br />to type, my one-and-only concern is ease of = use.<br /><br />It's only after a program has parsed such data that the p= rogrammer can <br />produce versions of the file in various formats.<br /><br />And yes, I do use JSON, but only where I c= an call a library module (in <br />Perl) from one of my CGI scripts (also= in Perl, based on Mojolicious), <br />to turn a data structure into JSON= so when that data is sent to the web <br />client (typically a browser [= *]), the data structure can be easily <br />decoded by Javascript.<br /><= br />[*] Just for the record, some web clients are not browsers. In fact = <br />millions of them are not browsers.<br /><br />I have finished the p= arser, and almost finished the whole program. <br />Progress is here:<br = /><br /><a href=3D"http://savage.net.au/misc/wikipedia.01.png">http://sav= age.net.au/misc/wikipedia.01.png</a><br /><br /><a href=3D"http://savage.= net.au/misc/nationalgeographic.01.png">http://savage.net.au/misc/national= geographic.01.png</a><br /><br />Ignore the fuschia boxes. They are just = inserted to make it easy for me <br />to deal with the remaining problem = of overlapping text.<br /><br />As you can see, I've figured out how to shift the text when it overlaps, <br />but I have not = yet shifted the corresponding connecting lines. Hey! It's <br />only 8:17= am here now. I'll update the images during the day.<br /><br />And the s= caffolding nodes, whose names are digits, will obviously be <br />suppres= sed later.<br /><br />The output you see is generated purely by default o= ptions within the <br />program. There are almost a dozen options so far.= All the user has to do <br />is provide the *.clad files above. Simple!<= br /></pre></blockquote></div></body></html> ------GYUH81625AYLCJTV9FKWIYRLDQRD96-- --===============6109899484697617978== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ [email protected] http://lists.research.att.com/mailman/listinfo/graphviz-interest --===============6109899484697617978==--