XML / XSL

sorry i already gave u this answer "No matter where you go, there your are..." - Buckaoo Banzi -pete

yep thats pretty much the best way to do it. the reason you need to create and instance of folder (CreateFolder) for each item is that AppendChild is appending a reference to the folder, rather than copying it. the way you could speed/simply life is to create a template node and use CloneNode: XmlElement templateFolder = doc.CreateElement("folder"); XmlElement folder; // Add first node folder = templateFolder.CloneNode(); folder.SetAttribute("name", "folder 1"); folder.InnerText = "1st Node"; root.AppendChild(folder); // Add second node folder = templateFolder.CloneNode(); folder.SetAttribute("name", "folder 2"); folder.InnerText = "2nd Node"; root.AppendChild(folder); hope this helps "When the only tool you have is a hammer, a sore thumb you will have."

XSL is the group name for XSLT and XSLFO really its XSL-T and XSL-FO T was the transformation part - translating and xml document into another document. FO was the formatting objects part - defines the presentation of an xml document for page layout. however since XSL-FO took so long to arrive every tends to use XSL to mean XSLT. "When the only tool you have is a hammer, a sore thumb you will have."

I read it! (better late than never ;P ) - Nitron "Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb

I didn't know you were so into XML. Maybe another Soda Springs venture may be in order... :suss: - Nitron "Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb

I would store your data within a class using std::vector to dynamically allocate your "branches" within the program. Then you can create a class using iostreams to write the data to a file in XML format. Then use something like PugXML (somewhere here on CP, I'm too lazy to look) to get the data back. - Nitron "Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb

You need to pass an XmlWriter to the Save method: void SaveXml(XmlDocument doc, Stream s, Encoding encoding) { XmlTextWriter xtw = new XmlTextWriter(s, encoding); xtw.Formatting = Formatting.Indented; xtw.Indentation = 1; xtw.IndentChar = '\t'; doc.Save(xtw); } "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Hi Palbano, thank you very much for the reply, I understood that the DOM is already a tree struture, what I'd like to do is to transfer these data into another structure written in C/C++, which unfortunately I'm very terrible at. Would it be possible if you can show me how this is done by providing an example skeleton code. Much appreciated!

Christian Graus wrote: I can't remember, is it 0 or 1 based, the indexing ? 1 based --Mike-- The Internet is a place where absolutely nothing happens.   -- Strong Bad 1ClickPicGrabber - Grab & organize pictures from your favorite web pages, with 1 click! My really out-of-date homepage Sonork-100.19012 Acid_Helm

Nevermind, sorry, thanks Wrong path in.xsl deleted "TEAMS/" Later, JoeSox www.joeswammi.com Load my Sig here.....

Ok, that didn't come out right. I've changed the brackets to <- and -> so the code would show. Sorry about that. <-xsl:for-each select="MyDataset/Table"-> <-xsl:text disable-output-escaping = "yes"-> <-z:row LastName="<-/xsl:text-> <-xsl:value-of select="LastName"/-> <-xsl:text->" OrderTotal="<-/xsl:text-> <-xsl:value-of select="OrderTotal"/-> <-xsl:text disable-output-escaping = "yes"->"/><-/xsl:text-> <-/xsl:for-each->

Hi Bernd Thanks for this but the problem here is that XForms is not yet a standard and I need to get something implemented fairly soon.

Right. I had found that one. I was hoping somebody would point out the magical-yet-hidden "merge" method on the IXMLDOMNode interface. :) I guess I'm going to have to do it by hand. J May the bear never have cause to eat you.

Try google. There are a couple of implementations, including IE plug-ins. I haven't tried any yet. In howfar any of these implementations allow for XForm-driven standard Windows dialogs (as opposed to browser-based forms) remains to be seen. I am interested in that, too. What makes XForms superior to approaches like XUL is that no or little scripting is required. XUL, appart from being tied to Gecko, still requires JavaScript for event handling and inter-control dependencies. Having just said that; W3C specifications are a dull reading and I have another ~200 pages to go on the XForms 1.0 spec. Bernd

Heya, either change the XSL to: ... ... or, since you seems to make a copy of the stuff use the xsl:copy-of element. Cheers /WW