XML

[Ivers, Doug E]

Looks like most of the functions require a docID as the first parameter.  This seems a bit onerous if my stack never loads an external XML doc.

To what extent is the loaded XML doc acting like a built-in Rev object -- on par with cards, fields, buttons, etc.?  Is this the intent of the Rev/MetaCard programmers?


-- D


> -----Original Message-----
> From: Sarah [mailto:sarahr at genesearch.com.au]
> Sent: Tuesday, September 03, 2002 6:03 PM
> To: use-revolution at lists.runrev.com
> Subject: Re: XML
> 
> 
> The docID is just a label that gets assigned to your XML 
> document once 
> it is read. You can have more than one document open at a 
> time, so this 
> docID tells the command which document to use for each operation.
> 
> Sarah
> 
> On Tuesday, September 3, 2002, at 10:32  pm, Ivers, Doug E wrote:
> 
> > I've been trying to figure out how the xmltree-view.rev 
> works (the XML 
> > demo that comes with 1.5A7).  I don't understand the docID 
> thing.  The 
> > docID number seems arbitrary once the file is loaded.  (I'm 
> a beginner 
> > with XML, so I might be showing my ignorance -- I'm not 
> sure what is 
> > Rev specific versus standard XML.)
> >
> > One thing I'd like to do is extract (or create from 
> scratch) a field 
> > that displays an xml tree in outline form -- independent of 
> anything 
> > else, as would be appropriate for a library object.
> >
> > Any suggestions, tips, insight?
> >
> >
> > -- D
> >
> >
> > _______________________________________________
> > use-revolution mailing list
> > use-revolution at lists.runrev.com
> > http://lists.runrev.com/mailman/listinfo/use-revolution
> >
> 
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>