Phil Davis wrote:
>> The benefits of XML are many, at least as a format for exchanging
> data
>> between applications.
>>
>> On the flipside, for use within an application I find it hard to
> beat the
>> speed and convenience of using MC's custom properties. MC's
> interpreter is
>> fast, but not as fast as it's compiled code for getting and setting
>> properties. And with multiple property sets within a rich object
> hierarchy,
>> one can implement complex hierarchical data structures quite easily.
>
>
> Concept: what if MC could automatically convert an XML document to an
> array or set of arrays? And convert arrays to XML?
>
> Would there be a way to set up the new "split" and "combine" commands
> to parse/unparse an XML document into/out of an array or set of
> arrays? That would be about as cool as it gets, no?
With one hitch: XML is inherently n-levels deep in terms of nesting, while
MC custom props are only one level deep (conceivably two if you include
multiple data sets). The key to getting depth with MC is to use the object
hierarchy in conjunction with custom prop sets, and while that's more depth
than most people will need it will, being a fixed number, not be able to
directly address some XML needs.
Another Q: Are you folks creating and parsing DDTs with your XML, or just
dropping tags in without regard for the DDT component?
--
Richard Gaskin
Fourth World Media Corporation
Multimedia Design and Development for Mac, Windows, UNIX, and the Web
_____________________________________________________________________
[EMAIL PROTECTED] http://www.FourthWorld.com
Tel: 323-225-3717 ICQ#60248349 Fax: 323-225-0716
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
