Kerry,
Howzabout DOM-Lingo: a complete DOM Level 2 implementation in Lingo? My
implementation parses XML into DOM trees, and provides the entire Document
Object Model API to access, travserse and edit the nodes in that tree. That
includes methods relevant to your needs -- like getElementsByTagName( ),
which returns a NodeList object containing all the Element nodes in the tree
that match a given tag name. DOM-Lingo also implements the methods of the
Traversal module, so you can use NodeIterators and TreeWalkers to walk the
DOM. You can create XML documents in memory, from scratch, too. Then call
the Views module methods to output canonical XML.
Andrew White's Lingo parser, bless his soul, does not provide a "much more
usable property list", because one of its aims was to completely reproduce,
verbatim, what the makeList( ) method of the XMLParser Xtra returns. It was
also meant to circumvent the bugs in the XMLParser Xtra at the time. What
his parent scripts DO provide is a more usable API for accessing a native
node tree built by his Lingo-based parser. But that API was baked in his own
oven, and doesn't really follow any standard (like the DOM). It does the
job, but doesn't shoot for a target that is substantially higher than that
which the XMLParser Xtra hits.
There may be other XML node parent scripts out there, but none of them are
as comprehensive or robust as DOM-Lingo. It sounds like it's something you
need. If you'd like to preview it, I'd be happy to send it to you.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Christopher Watson
Sr. Software Engineer
Lightspan, Inc.
http://www.lightspan.com/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-----Original Message-----
From: Kerry Thompson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 28, 2001 2:31 PM
To: [EMAIL PROTECTED]
Subject: Re: <lingo-l> Repeat properties
>I'd like to take this opportunity to point out that
Jakob/Jacob can be
>spelled in different ways.
As can Kerry :-)
>Some Jakobs get hurt when their particular spelling is not
respected
Ok, folks, we gotta respect Jakob's feelings. -I- spelled it
right--what's
wrong with the rest of you ;-)
>And are you sure you really want to traverse this info in
the property
>list domain rather than in the xml-node domain?
No, I haven't made that decision yet. A lot depends on
whether I can
retrieve multiple child nodes with the same name. I
understand Andrew
White's xml parser gives a much more usable property list
than
Macromedia's, so it also depends a lot on that.
One of the list's more prominent denizens sent me some code
for a parent
script that creates xml node objects--that's another
possibility.
[To remove yourself from this list, or to change to digest
mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to
the list,
email [EMAIL PROTECTED] (Problems, email
[EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo.
Thanks!]
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
