I've started doing my multipage forms as single Tapestry pages with a
pageNum property to tell which page I'm on. For example,
<span jwcid="@If" condition="ognl:pageNum == 1">
<!-- put page 1 code here -->
</span>
<span jwcid="@If" condition="ognl:pageNum == 2">
<!-- page 2 here>
</span>
Just remember to either make the properties you have to remember
throughout the several pages persistent, or include them as hidden
field in subsequent pages' forms. The big advantage of doing stuff
this way is that you have access to the whole form from a single page
and can write all your handler code without major gymnastics.
If someone has a reason why this is a bad idea, let me know, please.
Todd
On Feb 5, 2006, at 11:02 AM, Archie Cowan wrote:
I've begun evaluating Tapestry for use in some applications that
will make
heavy use of multipage forms. I've gotten familar with the component
concepts, basic forms and validation with Enjoying Wed Development
with
Tapestry (Excellent tutorial btw). I've found several conversations
regarding integration of Tapestry and SWF and from the SWF change
log that
it has Tapestry integration built in now. But being new to both
frameworks,
I haven't found it obvious how the two fit together yet. Are there
examples
of this combination or articles available? If anyone can share how
they've
managed page flow in their Tapestry apps this is also very welcome!
TIA
Archie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
