Just cannot help it; I am sorry, just cannot keep it inside ;) On the
other hand, maybe not everyone knows about it yet?

Homepage: http://www.superinterface.com/easywizard.htm
Live demo: http://www.superinterface.com/wizard/signupWizard.do

Now back to the regular programming (c) Frank ;-)

P.S. The source code on the website works ok, but I am preparing a new
version now, which is better integrated with Struts and with my
two-phase DialogAction class.  It its current state it already handles
things like Back button and or view/model synchronization like nothing
else does. Word.

On 6/22/05, Michael Taylor <[EMAIL PROTECTED]> wrote:
> Alternatively, you can use one action form in session scope with a
> series of actions representing each page.  Each page in the wizard would
> have a series of forward representing the transition links from that
> state to others, basically modeling a FSM with actions as states and
> forwards as transitions.  This works well, with configuration of "next"
> and "previous" being pushed out into the struts configuration file.  If
> you need the list of valid pages to transition to filtered, you can do
> this with a little logic in a) the form, b) the action, or c) a tiles
> controller that pre-processes the GET request for the form and
> additively or subtractively controls which navigation paths are visible
> on the page.  I've done this several times entirely in struts for
> different "wizard" flows.  I've always wound up coding the state
> transition guards in Java, which is why an alternative like Spring flow
> might be even better.
> 
> Cheers,
> 
> Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to