Ken, other than being smaller (no external), and having extensive documentation, what are other advantages of your xmllib over the new revXML* functions included in Rev 2.x?
You can customize the way XML is handled to suit special cases (like
MTML ;-), and many people have told me it is easier to understand and
use than the revXML functions. It also used to be that this was the only
XML library MetaCard users could use (unless they also happened to have
Revolution), but that point is moot now.
Keep in mind, though, that revXML is an external, and is therefore faster than a Transcript-only solution; it also supports SOAP, DTDs, etc. and is better at reading large quantities of "records" from a "database" XML document.
Ken Ray
Re: You can customize the way XML is handled to suit special cases (like MTML ;-)
Ken
I just looked through the docs for this. It looks like one of the important steps in using this involves validation of the document as valid-XML, well-formed and all that neat stuff. 1. MTML is not well-formed. 2 MTML is designed to work with fragments of itself broken up into smaller sized objects. For an example: I would need to isolate a set of XML sales transactions with each transaction becoming a document fragment, object, and then parse just that fragment without validating the XML of that fragment first.
Can your XML external customize to the point that it will work with #1 & #2 ?
If I were to get your open stack version would the source code be exposed so that I could see your perl regEx functions/handlers?
Thanks,
Mark
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
