Maybe have a look at Slide. You should be able to find it at Google code. Best Ralf.
On Tue, Feb 3, 2009 at 7:44 PM, João Saleiro <[email protected]> wrote: > > Hi, > > I have "a complex" Flex application composed with modules, viewstacks within > viewstacks, states, etc. I am working hard to keep the application as simple > as possible - and until now it's looking amazing. > I'm currently using "dumb views" (they know nothing about the framework - > Mate -, and it's up to the framework to inject properties on the views). > > I don't want to stick with the Flex navigation mechanisms. I would prefer > relying on some kind of design pattern / best practice solution to handle > application navigation. In another words, the framework should be > responsible for changing the application state, and the views should somehow > reflect that state change. > For example, imagine that I'm on module 1, 3rd view, state b, and by some > reason I want to execute some business rule that would result on a jump to > module 4, 1st view, state h. > Is there a design pattern that could be helpful to achieve a clean > navigation? > > > Thanks, > > João Saleiro > > CTO @ Webfuel > Adobe Certified Expert > Adobe Community Expert > Co-founder of the Portuguese RIA Community > > > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
