You could patch the ticker to return the data in its flat record, parent pointer form instead of as a recursive data structure. Building the tree from the flat structure is a lot easier than reading the nested XML.

And now ive patched the ticker to do just this. And return some additional information. Try using 'flattree=1' to get the new output. Also, the ticker now responds to xmlstyle settings and has the customary info tag with data about the ticker and stuff like that.

You can build a fully connected tree structure from the "flattree" output quite easily. The algorithm is as follows:

my $res = $o->pm_get( node_id => 180684, id => 505536, flattree => 1 ) +; my $data = XMLin( $res->content, ForceArray => 0 ); my %nodes; foreach my $node ( @{ $data->{node} } ) { my $nid = $node->{node_id}; # register this node so children can find it $nodes{ $nid } = $node; if ( my $pid = $node->{parent_node} ) { # tell the parent about this child $nodes{$pid}{kids}{$nid} = $node; # make the reference to the parent "hard" and not "soft" $node->{parent} = $nodes{$pid}; } }

You are guaranteed that this will work. You dont need to worry about the parent not existing, or anything like that.

---
$world=~s/war/peace/g


In reply to Re: How to simplify the datastructure returned by XML::Twig by demerphq
in thread How to simplify the datastructure returned by XML::Twig by davido

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.