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 navi
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 i
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) wo
Thanks v much Johannes - Command was the only pattern I had considered thus
far because I know it's often used for history/undo functionality -
interested to look at memento in conjunction. Useful info as always :)
On Thu, Jan 22, 2009 at 12:08 PM, Johannes Nel wrote:
> Depending on the applica
kind of off topic now.
i would actually look at slide, even for an existing app (if it uses
viewstacks and states) for navigation. it makes life much much easier.
Slide uri's map to paths inside a display tree so the url
/app/state/stateb/statec tells you that you have set the selected child for
Johannes, does slide Slide work well with modules as this project is
modular?
On Fri, Jan 23, 2009 at 7:46 AM, Johannes Nel wrote:
> kind of off topic now.
>
> i would actually look at slide, even for an existing app (if it uses
> viewstacks and states) for navigation. it makes life much much e
we have never had a problem with modules, there are no singletons,
controllers and models cascade through the display tree (with the ability
overwrite these references anywhere down the display tree) and modules are
just new children on the display tree.
it is not a framework in the sense of cairng
7 matches
Mail list logo