Hi there, Sean.
Yes, odd indeed.
My implementation does not yet create new XML documents from property lists,
but that was one of my goals for the "newChild" method -- an optional
argument for a nested property list (from XMLParser, for instance) that
reformed the XML. My parent script just provides an API to creating and
manipulating child objects that act as XML document tree nodes, and then a
singular method for recursing/traversing the tree and concatenating the
textual XML. You could FileIO that out to an external XML document.
No link for it, unfortunately, but I can certainly forward it to you
directly.
> Odd how these synchronicities occur. I have been in the process of
creating
> XML definitions for behavior properties and looking for a way of exporting
> existing property lists into an external XML document - when you appear
with
> what looks like a part of the puzzle I'm needing to implement.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Christopher Watson
Sr. Software Engineer
Lightspan, Inc.
http://www.lightspan.com/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
[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!]
