velocity-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "G.L. Grobe" <g...@grobe.net>
Subject Re: can method params be javascript?
Date Wed, 03 Jul 2002 03:34:23 GMT
Gier, heh, thanks ... I understood that part. But it was Mike's solution to
moving the logic to the server side that I didn't understand, or at least in
the scenario I'm trying to use it in. To try to be clearer, it was the
solution itself I didn't get.

> > I didn't understand the point on moving the logic to the server side.
Though
> > I can see how what I had tried to do would not work because the parsing
is
> > on the server side. To clarify the problem, here's what it is I'm trying
to
> > do ...
> >
> > When the user goes to pageA, a <select ...> element using a velocity
method
> > populates the <option ...> values. Then using an onChange() from that
> > <select ...> element, I'm trying to pass the <option ...> value that
was
> > selected and pass it into another velocity method that will filter a
dbase
> > query so as to populate the second <select ...> element's list box. Then
do
> > the same w/ a third <select ...> from the selection of the second.
> >
> > Any help much appreciated.
>
> The Velocity code gets executed on the server, when the page is rendered
and
> sent to the client.
>
> The Javascript, such as onChange(), is executed after the page has arrived
> at the client, so at this point, all the Velocity processing is done.
>
> Does this clear it up?



--
To unsubscribe, e-mail:   <mailto:velocity-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:velocity-user-help@jakarta.apache.org>


Mime
View raw message