Mailing List
Home
Forum Home
Softimage
Carrara
trueSpace
Dir3d-l
Maya - a powerful 3D animation and visual effects software
Macromedia Flash Development
Subjects
Cameras
scaleDown command
black out solved
Aircraft Tutorial
Mathematical XYZ ?
Its done This vs That
Its done first week
recommendations for screen video captures?
3DExplorer "Oddity "
New Director
ProTeam renewals
Fuel 's new websites (X post)
Blue peter create a make toy
targeting groups question
XPost: Shockwave 3D game ( sort of )
RES: RES: RES: Fish Modeling
Emitting particles from object intersection
Fuel 's new websites (X post)
Texturing
Big Break Contest Videos
New Plugins
Models and Texture on my updated site
Error Installing Patch tS6 6
Plasma?
Looking for Inspiration
Weird EMail Q
It 's done first week ?
Cherry not cranberry
New game
Camera Animation Problem
Particle plugins?
 
Freeware ActiveX XML parsers

Freeware ActiveX XML parsers

2005-05-03       - By Brad Friedman

 Back
Reply:     1     2     3     4     5  

no one is more surprised than I that I have a recommendation... or at
least some useful information (I was sure I was gonna be a rigger... not
a programmer... wrong again).

I took a quick look at the Chilkat XML docs to make sure.  And I think
that particular parser is a DOM style  parser.  Which has repercussions.

Stepping back a second.

According to w3c there are two basic types of XML parsers (well, two
that they foresaw and wrote about).  DOM type and SAX type.

DOM (Document Object Model) type parsers will parse the entire XML file
and load it into memory to be manipulated like a node tree.

SAX (Simple API for XML) type parsers are event driven.  As an XML
stream is read, it fires off callbacks to your code to do with the data
what you will.

(note: in most cases a DOM style parser is written on top of a SAX style
parser.  It uses the SAX parser to build the DOM tree and then hands it
over to you.)

Without a doubt, DOM parsed XML docs are a lot more fun and intuitive to
work with.  However, since the entire document ends up loaded into
memory in most cases, its not always reasonable to use a DOM style
parser on large data sets.  And since we are talking about 3d here...
large data sets are a possibility (dare I say likely?).

So, if you're looking for a good solid XML base to work off of for
working in XSI, I'd look to something that has both types of parsers to
work with.  Though I'm kinda new to the ActiveX world... so I don't have
any specific recommendations as to what might satisfy said suggestion.  
Though I'd be willing to bet Python has a number of good XML parsers
available.

-brad

Bradley R. Gabe wrote:

> Howdy List-
>
> I'm experimenting with some XML based toolsets in XSI and have been
> using the free Chilkat Xml parser which I'm finding to be faster than
> MSXML.
>
> Anybody out there have recommendations for other XML engines and
> editors, as well as file browsers, etc? This is all fun and new to me
> and may force me to use Python to take better advantage of its XML
> features. :-)
>
> Thanks
> -Brad
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following text in
> body:
> unsubscribe xsi


---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi