Cart
[Home] [By Thread] [By Date] [Recent Entries]
I have only just started getting some code together, I suggest you have a look at wxWindows where there is references to wxHtml which I was going to use. Most of what I will be doing will be from other's code, IBM have put source code to a Parser on the WEB, All that is available has to be sorted through and then integrated etc... for XML http://web.ukonline.co.uk/julian.smart/wxwin/ ----- Original Message ----- From: Cristobal Galiano Fernandez <c.galiano@u...> To: Trevor Croll <litebook@p...> Sent: Friday, July 16, 1999 7:09 PM Subject: Re: XML (Data Entry / edit screen) > Can you share with us your generic XML/XSL code for Data Entry / Edit > Screen. > We are beginners in this techologie > > Thanks in advance > > Cristóbal > > > > Trevor Croll wrote: > > > For about 4 months I have been looking for ways of XML ing the > > software I was planning to write. My conclusions may be of interest to > > others. My conclusion as how I should write my application is:for > > data definitions I start with a name space file ie namespace.xmlFor > > screen style sheet I may need another namespace file to help the user > > choose appearance. I then take XSchema, make some additions to it for > > input fields, field lengths, field types etc.....and develop a data > > entry interface that obeys this "new enhanced Xschema" This was the > > user can define their own fields and do a straight forward data entry > > / edit screen that would look similar to Access forms. I then use XSL > > definitions to "merge" the data with the XSL to produce HTML which in > > the short term I can use Internet explorer for viewing and printing > > until I have produced my own viewer. For reporting I need XQL which > > can run down a nindex file and pull in all items that obeys that index > > and examine them for the data in them. This builds an XML data string > > which then when an XSL style sheet defn is applied "merges" the data > > into a HTML document. For internet email transmissions there is two > > options: sent the HTML file, or send the XML data and XSL style sheet > > definitions so the package at the other end can produce the HTML > > view. The implications of this approach are:Must constrain all > > functions to produce acceptable HTMLdo not need XFA, XFDL, or any > > other not yet recommended standard. Have to produce an XSchema of my > > own, but since it is only used in my package it does not matter if it > > does not conform to any standards. > > xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
