Time to thank you Paul for pointing me in this direction, and for your help. I finally have some success.
Although i ended up going in a different order, eg html page (created by cgi app) with Javascript which sends the Query to the cgi app when the user types into the input, which in turn creates the data island, for the javascript to manipulate. What a way to finish on a friday, im going home (its POETS day after all) with the load off my brain. Thank you thank you ----- Original Message ----- From: "Paul A Norman" <[EMAIL PROTECTED]> To: "NZ Borland Developers Group - Delphi List" <[EMAIL PROTECTED]> Sent: Monday, December 08, 2003 4:09 PM Subject: Re: [DUG] webbroker and webservices > Don't know if this will fit your bill or not, may be its what you did, but > might be of interest to someone who hasn't checked it out. > > Much easier than masses of JS arrays of objects or heaps of variables: > > What about XML data islands in filtered tables or direct manipulaiton of > the XML either through JS or XSL.. stuff? Assuming client base is on IE 5+ > > Write whole pages **on the Clinet** from script applied to XML, highly > object orientated and not too much of a learning curve. > > Prerequisite: Need a bit of a working knowledge of the HTML document object > model and JavaScript or JScript (MS). > > Main dataset(s) droped inXML from Delphi. > Dataisland(s) set up in first page (HTML) can then be refered to in script > by Id, or created entirley in script. > > <xml src="blahblah.xml" id="firstXml" /> > > <script ...> > firstXml.dosomething(); > firstXml.dosomethingElse(); > .. > </script> > > You can create new pages on the fly directly from JS and use the XML data > under JS to fill the new pages as valid HTML code. Once you have got HTML to > open a new WINDOW you can access its DOCUMENT object, create elements give > them attributes, set attributes, css styles, set dynamic expressions .. .. > .. and content, and refer back to the parent window to carry out functions > there .. use XML tag contents and XML tag attributes. Also using JS 5.0 can > rely on XML 3.0 level for backward compatibility with IE 5 browser. > > Use multiple XML, download on demand, or during initial download. > > Initial download time overheads more than compensated for by the incredible > speed with which the rest happens, ** as it is all client side **. > > Very versitile for appropriate situations, and worth the learning curve. > Also the Mozilla DOM is developing to become usfeul and, in a growing > number of key areas, is drawing near to the MS model. > > I've found using JS better than XS?.. transformations as it gives you > complete control (and more features than the then (5.0) curent XS?.. > sometimes) and is easier to debug. > > Paul > [EMAIL PROTECTED] > http://PaulANorman.com > > Ph NZ 021 782 433 > Fx NZ 021 292 2433 > > Overseas: > > Ph. +6421782433 > Fax +64212912433 > > P.O. Box 1005 > Nelson 7015 > New Zealand > > =====brief excerpt from MSDN 2001 (c) Microsoft > XML Data Islands > There is an increasing need to be able to embed "islands" of data inside > HTML pages. In Microsoft� Internet Explorer 5.0 and later, these data > islands can be written in XML. > > The following topics describe the syntax used for embedding these data > islands within a page, and detail the object model exposed by the browser to > enable them to be used. This method of embedding XML in HTML follows the > note published by the Worldwide Web Consortium (W3C) as the "XML in HTML > Meeting Report." The W3C expects to evolve the HTML specification to include > the capability of embedding XML in HTML documents. > > Embedding an XML Data Island into an HTML Page > An XML data island can be embedded using one of the following methods. > > a.. Using the Dynamic HTML (DHTML) XML element within the HTML document > b.. Overloading the HTML SCRIPT element > Using the XML Element Within the HTML Document > This syntax is valid for Internet Explorer 5.0. > > There are two syntactically correct ways of using the XML element within the > HTML document. > > a.. The XML data can exist inline, surrounded by XML start and end tags. > <XML ID="XMLID"> > <XMLDATA> > <DATA>TEXT</DATA> > </XMLDATA> > </XML>b.. The XML element can have a SRC attribute, the value of which is > the URL for an XML data source. > <XML SRC="http://localhost/xmlFile.xml";></XML>The XML element is present in > the HTML Document Object Model. It is in the DHTML all collection and is > seen by the browser as just a regular node. The XML data within the XML > element can then be accessed by calling the DHTML XMLDocument property on > the XML element. > > The XMLDocument property returns the root node of the XML within the XML > element or the root node of the XML referenced by the value of the SRC > attribute. From this root, the XML data island can be navigated using the > XML Document Object Model (DOM). The following function returns the data > from the data island with the ID of "XMLID". > > function returnXMLData(){ > return document.all("XMLID").XMLDocument.nodeValue; > }The XML element can also be referenced by ID alone. For example, the > following function has the identical functionality as the preceding example. > > function returnXMLData(){ > return XMLID.documentElement.text; > }Because the XMLDocument property was not used, the documentElement > property must be called to retrieve the root element of the XML. > > _______________________________________________ > Delphi mailing list > [EMAIL PROTECTED] > http://ns3.123.co.nz/mailman/listinfo/delphi > _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
