From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-14016-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 31730 invoked by alias); 22 Oct 2009 14:52:56 -0000
Received: (qmail 31554 invoked by uid 48); 22 Oct 2009 14:52:44 -0000
Date: Thu, 22 Oct 2009 14:52:00 -0000
Message-ID: <20091022145244.31553.qmail@sourceware.org>
From: "chwang at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
In-Reply-To: <20090926214257.10697.chwang@redhat.com>
References: <20090926214257.10697.chwang@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug tapsets/10697] Tapset for generation of XML-esque data
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2009-q4/txt/msg00257.txt.bz2


------- Additional Comments From chwang at redhat dot com  2009-10-22 14:52 -------
(In reply to comment #4)
> (In reply to comment #1)
> > Created an attachment (id=4233)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=4233&action=view)
> > Current version of the markup script
> > 
> > Brief sketch of proposed script. Somewhat arbitrary/possibly inefficient in the
> > way it keeps track of open/closed tags and what needs to be printed.
> 
> Any thoughts on how we could use this with dynamic output?. I'm thinking of
> scenarios where we might want graphs to parse the output and update dynamically
> . We would need the xml output to be consistent/fully formed at all times , not
> sure if thats feasible..
> 
> 


I'm not sure how to keep the XML fully formed without using embedded C to insert
into a file, but maybe you can pretend that closing tags exist? I did something
similar to build a (really) basic real-time XML-esque grapher.

So for example the script outputs:

<tag1>
    <tag2>
        <tag3>

and the reader will read that as [the round brackets indicate are imaginary tags)

Read <tag1>:
<tag1>
(</tag1>)

Read <tag2>:
<tag1>
    <tag2>
    (<tag2>)
(<tag1>)

Read tag3:
<tag1>
    <tag2>
        <tag3>
       (<tag3>)
    (<tag2>)
(<tag1>)

In my case the closing tags didn't even matter except to keep track of which
node to append data/nodes to, so it worked out pretty well.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10697

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.