I am not trying to store the application state on the client side.
I guess there are more uses to hidden fields than just that.
How can I implement a web page that has a list of display-only
items, each one ended by a "delete" checkbox like:
"movie title 1" [ ]
"movie title 2" [ ]
...
(the square brackets above are the checkboxes and the
content between double quotes is readonly, not editable
text fields).
In my understanding, repeaters require an "id" field
whose content is sent along with the checkboxes state
upon form submission.
In the example above, there is no such id field (just HTML text).
The hidden fields would be used to store that unique id,
so the multiple delete upon checkbox selection would work.
How can I make this work with Woody?
Thanks,
jlerm
----- Original Message -----
From: "Leszek Gawron" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 08, 2003 12:42 PM
Subject: Re: Hidden form fields with Woody
> On Mon, Sep 08, 2003 at 12:37:54PM -0500, jcplerm wrote:
> > How can I set a field to be of type "hidden" with Woody?
> What do you need a hidden field for ? I used to use hidden fields only for
> storing the current application state on the client side. With flow you
just
> do not need it.
> LG
> --
> __
> | / \ | Leszek Gawron // \\
> \_\\ //_/ [EMAIL PROTECTED] _\\()//_
> .'/()\'. Phone: +48(501)720812 / // \\ \
> \\ // recursive: adj; see recursive | \__/ |
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
