Please remove me from your distribution list.
Thanks
-----Original Message-----
From: [EMAIL PROTECTED]@ENRON COMMUNICATIONS [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 11, 2001 9:05 AM
To: [EMAIL PROTECTED]
Subject: Re: ActionMapping Workflows
My first thought here would be to make this information available as a
helper object that would read the forwards from the ActionMappings and
bundle them up for the view. The view could then write whatever buttons
it liked by reference to the helper object and the logic tags. Of
course, someone could also develop a taglib that read the helper object
directly and automatically created a panel of buttons.
Dan Powell wrote:
>
> Another feature that might be nice to add here is the sense of optional
> actions. In this I'm thinking of the standard wizard interface, where
> there are three possible directions a user can travel through the
> workflow at any time: next, back, finish. If there are 5 actions total,
> with only the first three required, then on the first screen only the
> next direction would be possible. On the second screen, both next and
> back are possible. On the third screen, the finish button finally
> becomes active, in addition to next and back. On the fourth screen, all
> three are available as well. On the fifth screen, only the finish
> direction is appropriate. Some logic to determine which of these
> directions is possible would be helpful when building the ui, so as to
> know which links are appropriate to make available.
>
> --
> J. Daniel Powell
> Sr. Systems Architect
> Wellogic, Inc.
- att1.eml << File: att1.eml >>
