You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Guillaume Bodet <gb...@gmail.com> on 2013/03/26 12:38:24 UTC
Wizard Component
Hi all,
I'm looking for a wizard component for Tapestry 5.3.
By "wizard", I mean a conversational set of pages that can manage state and
transition rules (previous-next-cancel).
If no such component exists, does any of you have ideas about the right
design of such a component?
Best regards,
Guillaume
Re: Wizard Component
Posted by Lance Java <la...@googlemail.com>.
If you want to avoid @Persist, you might want to consider using one big
form on a single page.
You can then use javascript (and maybe a bit of ajax) to show/hide small
segments of your form at a time.
On 26 March 2013 13:50, Chris Cureau <cm...@gmail.com> wrote:
> To follow up on what Thiago has said... I've had good luck with thexe
> examples from the Jumpstart:
>
>
> http://jumpstart.doublenegative.com.au/jumpstart/examples/wizard/usingformfragments/$N/$N
>
> http://jumpstart.doublenegative.com.au/jumpstart/examples/wizard/usingpages1
>
>
> On Tue, Mar 26, 2013 at 6:59 AM, Thiago H de Paula Figueiredo <
> thiagohp@gmail.com> wrote:
>
> > On Tue, 26 Mar 2013 08:38:24 -0300, Guillaume Bodet <gb...@gmail.com>
> > wrote:
> >
> > Hi all,
> >>
> >
> > Hi!
> >
> >
> > I'm looking for a wizard component for Tapestry 5.3.
> >> By "wizard", I mean a conversational set of pages that can manage state
> >> and transition rules (previous-next-cancel).
> >> If no such component exists, does any of you have ideas about the right
> >> design of such a component?
> >>
> >
> > I think these requirements are too generic to build a component that does
> > that.
> >
> > The easier way of implementing something like that is to put all the data
> > in a single object and use @SessionState in the different pages or
> > components which comprise your wizard, so the same object is shared.
> >
> > --
> > Thiago H. de Paula Figueiredo
> >
> > ------------------------------**------------------------------**---------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<
> users-unsubscribe@tapestry.apache.org>
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
Re: Wizard Component
Posted by Chris Cureau <cm...@gmail.com>.
To follow up on what Thiago has said... I've had good luck with thexe
examples from the Jumpstart:
http://jumpstart.doublenegative.com.au/jumpstart/examples/wizard/usingformfragments/$N/$N
http://jumpstart.doublenegative.com.au/jumpstart/examples/wizard/usingpages1
On Tue, Mar 26, 2013 at 6:59 AM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Tue, 26 Mar 2013 08:38:24 -0300, Guillaume Bodet <gb...@gmail.com>
> wrote:
>
> Hi all,
>>
>
> Hi!
>
>
> I'm looking for a wizard component for Tapestry 5.3.
>> By "wizard", I mean a conversational set of pages that can manage state
>> and transition rules (previous-next-cancel).
>> If no such component exists, does any of you have ideas about the right
>> design of such a component?
>>
>
> I think these requirements are too generic to build a component that does
> that.
>
> The easier way of implementing something like that is to put all the data
> in a single object and use @SessionState in the different pages or
> components which comprise your wizard, so the same object is shared.
>
> --
> Thiago H. de Paula Figueiredo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Wizard Component
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Tue, 26 Mar 2013 08:38:24 -0300, Guillaume Bodet <gb...@gmail.com>
wrote:
> Hi all,
Hi!
> I'm looking for a wizard component for Tapestry 5.3.
> By "wizard", I mean a conversational set of pages that can manage state
> and transition rules (previous-next-cancel).
> If no such component exists, does any of you have ideas about the right
> design of such a component?
I think these requirements are too generic to build a component that does
that.
The easier way of implementing something like that is to put all the data
in a single object and use @SessionState in the different pages or
components which comprise your wizard, so the same object is shared.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org