Hi LLTYK :),
Thanks for the idea.
Yes, this could be the solution to preserve user input while
refreshing (not submitting) the form.
The drawback is: this will generate many traffic to the server.
Thank you for your help.
On Wed, Sep 22, 2010 at 6:07 PM, LLTYK <ll...@mailinator.com> wrote:
>
> The usual way to save input is to do a form submit. Link the form to the
> zone, and then submitting will trigger the update on the zone after sending
> the data to the server.
>
> However, this does not work if the form is not filled out and valid. In that
> case there's a longer way:
>
> I used the ZoneUpdater mixin on all the form components, not to update the
> zone but to simply record changes serverside (returning void from the event
> handler). Something like this:
> <t:textfield t:id="TextField" value="value"
> validate="required,minlength=3,maxLength=25"
> t:mixins="zoneUpdater" t:zone="thezone"
> t:clientEvent="keyup" event="change" />
> �...@log
> public void onChangeFromTextField(String value)
> {
> this.value = value;
> }
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
