|
|
write your, lets say, 5 pages with nav buttons. Look that they work fine
with navigating forth and back.
implement a visit object with, lets say, a public Map property, and set
it to be your visit in the .application definition.
write forms for your pages, using the map property of the visit to share
data between pages.
Good luck...
××××× Ed Greenberg:
Where would I look for an example, or an approach, on how to construct a
multipage wizard. This would accumulate part of a form submission on
each page, with next and back buttons. When the user hit the end of the
wizard, we would then call a final listener that would actually process
the request.
Perhaps I need my paradigm shifted. I don't even know what to call this
in Tapestry-speak :)
Any pointers?
</edg>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: tapestry-user-help@xxxxxxxxxxxxxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: tapestry-user-help@xxxxxxxxxxxxxxxxxx
|
|