I don't think we are talking about the same thing here. Take my wizard example:
A user is on page 4 of the wizard. They fill out the form half way, relize they forgot something on page 3 and click the back button. At that point what we want to do is capture whatever the state of the form on page 4 was at that point because later when they click next on page 3 we want to show the form on page 4 just how they left it. The back button does a form submit with the default form processing turned off. So to make the above work all you need is something like this : FormState state=Form.getState(); <=== this creates a state object that stores all formcomponent.invalidinput fields And later page 4 can do this: FormState state=wizard.getFormState(4); If (state!=null) form.setState(state); <== this would fill in the invalidinput properties of the form components controls. -Igor > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:wicket-develop- > [EMAIL PROTECTED] On Behalf Of Johan Compagner > Sent: Friday, September 09, 2005 1:52 PM > To: [email protected] > Subject: Re: [Wicket-develop] More button talk. > > this discussion starts to boil down to keeping state in a form which > will be used in a render phase again > without updating it to the models or do anything with it. > > This will be build (i think by me) as the first thing after we finalized > 1.1 > > Because this is a thing we really need (there is a bug report open for > this) > We need to be able to do things on in the browser like having a > selection change event on a select box > but when that happens we can't loose the form data a user already has > filled in. > > Currently we loose the data users put in because now we just generate a > link with the onchange > but the onchange should be a post but only to hold the submit values at > someplace in the form > but do nothing with it and call the interface method of the onchange > event. > > I don't get the binding but not validation completely > When is the validation then be done? > > Do you have a form that goes over multiply pages? And only when you have > reached the final page > the validation can be done? > If that is the case then the form should hold its values are long as > possible. (i can use the invalid_input field for that) > and only when you call validate it will be done. > > johan > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
