Darn, I just have to make a wizard for Wicket, have to keep promises... Anyway, this is my view on wizard/flow/state:
* A web resource has address (hence can be bookmarked) In Wicket resource is represented with Page object. * A user can navigate to any bookmarkable resource using address bar in the browser, therefore a resource has to decide by itself, what to display to the user, or maybe to redirect somewhere else. This depends on resource's state. * Therefore, I find idea of wizard/flow *between* bookmarkable resource unproductive, because resource's view depends on resource's state, not on some artificial "flow state". I don't see a reason why I should not be able to navigate resource A only because I just visited resource B. This ruins the whole idea of internet and hyperlinked resources. * To me, a wizard makes sense within one resource, it will have only one address (a resource address), and the view will depend on resource's state. In this case all wizard's state is retained automatically, since Wicket is a stateful framework. The only thing is to ensure that new instance of the Page object is not created when it is navigated to. * There is no page 4. There is a web resource (a Page object) with 4 states and 4 corresponding views (either separate HTML files or panels within one file). There is no way to navigate to page 4, but there is a way to change state of Page object to state "1", "2", "3" or "4". Then, when Page is rendered, an appropriate HTML or panel is displayed. Michael. On 9/27/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > The idea is pretty simple: capture the state of a form and be able to > restore it later. The state is the captured request parameter values. So for > example lets say you are on page 4 of a wizard and you click the back > button. I would like to capture whatever you already typed in w/out > validating or binding it and save it somewhere. Later when you comeback to > page 4 I would like to be able to restore that state. We were talking about > introducing an opaque FormState object that would hold this state and adding > getState() and setState() to the Form. > > -Igor > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:wicket-user- > > [EMAIL PROTECTED] On Behalf Of Eelco Hillenius > > Sent: Tuesday, September 27, 2005 11:03 AM > > To: [email protected] > > Subject: Re: [Wicket-user] Good way to back up form state? > > > > I must have missed that (unfortunately, I've been very busy with > > non-wicket stuff lately). > > > > What is the idea? > > > > Eelco > > > > > > On 9/27/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > Whatever happened to the discussion we were having about a > > > getFormState()/setFormState() is that grounded until 1.2? > > > -Igor > > > > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] [mailto:wicket-user- > > > > [EMAIL PROTECTED] On Behalf Of Phil Kulak > > > > Sent: Tuesday, September 27, 2005 8:54 AM > > > > To: [email protected] > > > > Subject: [Wicket-user] Good way to back up form state? > > > > > > > > Right now I (and some other people I think) are calling > > > > FormComponent.invalild() on each component to save it's state. I was > > > > wondering if maybe there could be a more elegant way to do this? > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by: > > > > Power Architecture Resource Center: Free content, downloads, > > discussions, > > > > and more. http://solutions.newsforge.com/ibmarch.tmpl > > > > _______________________________________________ > > > > Wicket-user mailing list > > > > [email protected] > > > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: > > > Power Architecture Resource Center: Free content, downloads, > > discussions, > > > and more. http://solutions.newsforge.com/ibmarch.tmpl > > > _______________________________________________ > > > Wicket-user mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: > > Power Architecture Resource Center: Free content, downloads, discussions, > > and more. http://solutions.newsforge.com/ibmarch.tmpl > > _______________________________________________ > > Wicket-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
