Best way to architect mini wizard like screens?

[cesar saenz <ja...@gmail.com>]

Hi to all, 
I'm currently working on a project that has many sections that act as
mini wizards, in other words an action requires a sequence of screens
to complete such as adding a new user.  I would like to be able to
reuse these mini-wizards in other applications.  What would be the
best way to architect this?  Would I be attaching many pages to a
single component or would I just have a bunch of components that work
together?

Thanks,
Cesar

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: Best way to architect mini wizard like screens?

[Randolph Kahle <ra...@variantia.net>]

I am glad you are raising this question.

I am currently trying to figure out how to extract elements of 
application state that are embedded in Tapestry into a state machine 
that resides behind Tapestry. My problem is the same as yours except my 
scope is the whole application.

To solve my problem I need to:

     * Trap user gestures and send them to a state machine

     * Based on user input, current state, and possibly feedback for 
other tiers, determine the next valid state

     * Based on the next valid state, create and display a Tapestry page 
(dynamically)

I'll monitor this thread to see if anyone has suggestions.

Regards,

Randy

On Dec 7, 2004, at 3:34 PM, cesar saenz wrote:

> Hi to all,
> I'm currently working on a project that has many sections that act as
> mini wizards, in other words an action requires a sequence of screens
> to complete such as adding a new user.  I would like to be able to
> reuse these mini-wizards in other applications.  What would be the
> best way to architect this?  Would I be attaching many pages to a
> single component or would I just have a bunch of components that work
> together?
>
> Thanks,
> Cesar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: Best way to architect mini wizard like screens?

[Jamie Orchard-Hays <ja...@dang.com>]

Components can't contain pages, so you're stuck making components to put in 
pages. Another approach would be to make a series of pages and stick them in 
a library that you could reuse.

Jamie
----- Original Message ----- 
From: "cesar saenz" <ja...@gmail.com>
To: <ta...@jakarta.apache.org>
Sent: Tuesday, December 07, 2004 3:34 PM
Subject: Best way to architect mini wizard like screens?


> Hi to all,
> I'm currently working on a project that has many sections that act as
> mini wizards, in other words an action requires a sequence of screens
> to complete such as adding a new user.  I would like to be able to
> reuse these mini-wizards in other applications.  What would be the
> best way to architect this?  Would I be attaching many pages to a
> single component or would I just have a bunch of components that work
> together?
>
> Thanks,
> Cesar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org