Subject: Re: [xsl] interpreting WML 1.3 content w/XSLT From: Robert Koberg <rob@xxxxxxxxxx> Date: Tue, 26 Dec 2000 12:19:34 -0800 |
You are not submitting a form. In the html you need to have a form and you must submit it: <head> <script> function submitMyForm() { myform.submit(); } </script> </head> <body> <form name="myform" method="post"> <input type="text" name="mytext"> <a href="javascript:submitMyForm();">submit</a> </form> this will send the input values to the server ----- Original Message ----- From: "Craig Pfeifer" <cpfeifer@xxxxxxx> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Sent: Tuesday, December 26, 2000 11:58 AM Subject: [xsl] interpreting WML 1.3 content w/XSLT > All -- > > I'm trying to transform some wml 1.3 content into HTML, but I'm having a > problem with interpreting forms and variable resolution. > > Most WML forms I have seen use markup like the following: > > <p> > Symbol: > <br/> > <input name="v36" value=""/> > <a title="Submit" > href="http://ye.yahoo.com/http://finance.yahoo.com/q?s=$(v36:escape)"> > Submit</a> > > </p> > > Here, we see that the input field's name is 'v36', and the data from this > field in placed into the URL by the WML browser by variable substitution > ( $ precedes a WML variable reference) when the user 'submits' the form > (by executing the hyperlink). This is a case I think I can handle, but > gets complicated by the fact that WML doesn't have an enclosing form > element. > > This is the problem that I run into: > > <card title="Search"> > <onevent type="onenterforward"> > <refresh> > <setvar name="U" value="/exec/obidos/ct/text/vnd.wap.wml/-/"/> > <setvar name="T" value="tg/aa/wml/uk/"/> > <setvar name="S" value="subst/aa/wml/uk/"/> > </refresh> > </onevent> > <do name="ok" type="accept" label="OK"> > <go > href="$(U)$(T)searchall/-/blended/$(item:escape)/1/202-6049706-5439020"/> > </do> > <p mode="wrap" align="left"> > Please enter search word(s): > <br/> > <input name="item"/> > <a > href="$(U)$(T)searchall/-/blended/$(item:escape)/1/202-6049706-5439020">Go</ a> > </p> > </card> > > Here I am up a big creek, because the variables are defined in one scope > and referenced in another! I can't use xsl:variable, because if I try to > create a variable of global scope (i.e. not in a template), I can only > assign it once, and if I create a template to read in and assign all of > the setvar elemets, they will be out of scope when I process the next > element. > > I'm afraid that I'll have to do this w/DOM or SAX parsing... > > Any ideas? > > Thanks, > > Craig > > > -------- > Craig Pfeifer > www.cpfeifer.org > > > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] interpreting WML 1.3 content , Craig Pfeifer | Thread | [xsl] text/table wrapping and netsc, Thanasis Mastrogiann |
[xsl] interpreting WML 1.3 content , Craig Pfeifer | Date | [xsl] text/table wrapping and netsc, Thanasis Mastrogiann |
Month |