RE: [xsl] I have the XSLT, now need to make it usable as user-inp ut form?

["Kathy Burke" <Kathy_Burke@xxxxxxxxx>]

Hi Betty,

I realize some programming is needed, but I wanted to use an XML/HTML form
created using XSLT (this part is all done), then (using VB et al) save the
entire XML instance to a field in a database, then call upon that info using
XSLT etc. I'm familiar with VB, but how does one save the entire
Instance...that specific info is what I'm not getting. Otherwise, I may as
well go back to the old field-by-field database programming approach...?

Thanks.

Kathy

-----Original Message-----
From: Betty Harvey [mailto:betty@xxxxxxxxxx]
Sent: Tuesday, April 22, 2003 11:15 AM
To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'
Subject: RE: [xsl] I have the XSLT, now need to make it usable as
user-inp ut form?



Kathy:

	You need to write a program to do what you need to do.  This
depends on your environment and what you have internally to write the
with.  You can use Perl, Java, VB, etc. I have found PHP works very
nicely.  XML doesn't do programmatic procedures, it contains the data
you need to process the data externally.  

There really isn't any difference between an XML and HTML form.  In
the HTML form, there always needs to be a program behind the "Submit"
button.  This is also true for XML.

Betty
betty@xxxxxxxxxx
410-787-9200

On Tue, 22 Apr 2003, Kathy Burke wrote:

> >I'm not sure if it's actually possible to "save" the data before they 
> >submit the form. I've never heard of a web technology that does that ..
> 
> By "save" I actually meant to submit the form repeatedly in order NOT to
> lose any user input (the same document could be in use for hours), also I
> need to capture system time repeadetly for each "step" that is checked
> off...hoping to do that using an attribute on the <step>
element...somehow.
> 
> Anyway, the sad thing is I can tranform the xml data I need and make it
look
> pretty...but can't seem to get my brain around saving the xml instance of
> any give doc.
> 
> Thanks for your input.
> Kathy
> 
> 
> -----Original Message-----
> From: S Woodside [mailto:sbwoodside@xxxxxxxxx]
> Sent: Saturday, April 19, 2003 12:49 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] I have the XSLT, now need to make it usable as
> user-input form?
> 
> 
> Kathy, what are you using? Javascript? is this xslt being applied 
> server side or client side? do you have a toolset or rolling your own?
> 
> I'm not sure if it's actually possible to "save" the data before they 
> submit the form. I've never heard of a web technology that does that ..
> 
> that said, using xslt you'll use the same techniques you use for any 
> other forms in HTML. I agree, stay away from Xforms for now, they are 
> not "there" yet in the browsers. as far as checking the data, you must 
> do it on the server side for security, I'm not sure exactly how you 
> might accomplish that if it's a data-integrity problem, you could POST 
> to a regular CGI and do the checks there, or potentially there might be 
> some system available that uses a schema to check the results (using 
> W3C XML schema data types maybe).
> 
> simon
> 
> On Friday, April 18, 2003, at 09:51  AM, Kathy Burke wrote:
> 
> > Happy Friday!
> >
> > With much help from this list, I've now got a quite nice html output 
> > form
> > based on an xsl stylesheet for a work instruction (step-by-step) etc.
> >
> > I've been reading a lot of posts re: xforms, etc., but it doesn't look 
> > as if
> > I could use my xsl (which would be unthinkable!).
> >
> > My head is spinning...I could really use some
> > pointers-in-the-right-direction for how to best/most easily accomplish 
> > the
> > following:
> >
> > The xsl/xml instance presents the user with an html form of process 
> > steps to
> > follow. Each step has a checkbox (when checked I want to store the
> > SystemTime in an attribute value), and there are several user input 
> > boxes
> > along the way. When any user input is made, I do need to either check 
> > the
> > value against the xml attribute (e.g., high/low) and/or record the 
> > data (in
> > case it gets lost before a final form POST. My thought was to SAVE the 
> > xml
> > instance each time the user action occurs, overwriting the xml file 
> > each
> > time until the end of the process is reached.
> >
> > Does this make sense? Please point me in the right direction. How to 
> > capture
> > data as the user goes along AS AN XML INSTANCE? and how to assign a
> > system(time) variable to an element attribute (many occurences in the 
> > same
> > document).
> >
> > Thank you!
> >
> > Kathy
> >
> >
> >
> >  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> >
> >
> 
> --
>       anti-spam: do not post this address publicly
> www.simonwoodside.com -- 99% Devil, 1% Angel
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list