Actually, when you look closer to the whole continuation thing, continuations are not so incompattible with how Wicket works now. The original idea of continuations is to never return a value, but pass a context object (continuation) to the next function call. That idea translated to webapplications seems to be to have a 'wait-for-input' concept, so that you can model a flow like a couple of linear steps that conceptually 'pause'/ wait for input before it moves to the next step. As Wicket has a current state and does not work with return values for flow, I think we could defend that we do the same thing as the original definition, though with a slightly different flavor. At least it has the same net effect. And... if you want to do the web variant of continuations... that's easy... just create a mini framework that handles the flow and - I think - you're done.
Or... maybe I don't get the idea of continuations just yet. Please correct me if that is the case :) Eelco On 9/29/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote: > Isn't this looking like continuations? Also I have noticed in the same thread > the `wizard´ word > which is usually associated too with continuations. > > Am I wrong? > > ./alex > -- > .the_mindstorm. > > #: Igor Vaynberg changed the world a bit at a time by saying on 9/27/2005 > 8:38 PM :# > > 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 > ------------------------------------------------------- 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
