Depending on the application type, the command pattern works quite nicely with navigation. You can then also implement a memento more easily and have the command support an "undo" function allowing you to go back and forth.
we use slide (obviously) and the uri based navigation (based on states) work really well with this approach as well. On Thu, Jan 22, 2009 at 11:02 AM, nwebb <[email protected]> wrote: > Thanks guys for all your responses so far. > To clarify, it is a multi-step process (with a few possible branches). > > Tracy/Jim, for the most part I agree. Ideal if I was given the scope to > re-design the application, but I've just been handed the task of re-writing > the step-process logic. The client is very happy with what they have, so it > is a decision that is out of my hands. > > I am mainly looking for suggestions for (code) design > patterns/micro-architectures out there that handle this sort of thing - not > a fully-fledged framework. > > I did like the look of the book Haykel recommended, even though it was not > code-based so I may well purchase it too - thanks. > > Cheers, > Neil > > > > > > > > On Wed, Jan 21, 2009 at 9:02 PM, jim.abbott45 <[email protected]>wrote: > >> >> FWIW, I have to concur with the advice that Tracy gave you and I can >> also recommend--HIGHLY--the content at the link that Haykel gave you. >> >> In short, use Wizard-style navigation for >> infrequent/complex/inherently multi-step tasks. For the rest of >> (usually, most of) your tasks, use a more fluid navigational >> mechanism, such as Hub-and-Spoke. >> >> --Jim >> >> >> --- In [email protected] <flexcoders%40yahoogroups.com>, nwebb >> <neilw...@...> wrote: >> > >> > Hi, >> > >> > We have a modular Flex project. >> > Each screen has "back" and "next " buttons. >> > >> > There are various routes through the application and I'm about to >> re-write >> > the logic which determines where the buttons take the user when they are >> > pressed (what is already in place is overly complex). >> > >> > I'm guessing that there are fairly established methods for achieving >> this >> > and would be interested to see what exists, rather than roll out a >> bespoke >> > solution. Can anyone point me in the direction of a good resource? >> > >> > Cheers, >> > Neil >> > >> >> > > -- j:pn \\no comment
