We have worked with PureMVC in several projects. It's definitely better
than Cairngorm, especially the multicore support for big modular
applications, and the fabrication extension for loosely coupled
communication between modules.
We are working currently with Mate, and in our opinion is by far the
cleanest, simplest and fastest-to-develop-with framework from the ones
we've tried.
By the way, our evolution was ARP -> Cairngorm -> PureMVC ->
Mate .
Anyway, I am not asking for a specific framework, but for design
patterns for dealing the navigation inside the application. This is a
common problem - all applications need navigation - so there might be a
common solution.
The slide-framework has some information on the it's docs that help a
bit understanding the problem, but it's not exactly what we're looking
for.
João Saleiro
CTO @ Webfuel
Adobe Certified Expert
Adobe Community Expert
Co-founder of the Portuguese RIA Community
Scott Langeberg wrote:
multicore support? Is that a real feature, in a
single-threaded flash player?
On Wed, Feb 4, 2009 at 5:00 AM, Bachir El
Khoury <[email protected]> wrote:
Very powerfull framework with gsm finite state machine,
multicore support and it's been ported to almost all popular languages.
Thank you Ralf. Found it, and I'm taking a
look at the docs and
implementation. I don't know if I'll follow it, but it's an interesting
reading, for sure.
João Saleiro
CTO @ Webfuel
Adobe Certified Expert
Adobe Community Expert
Co-founder of the Portuguese RIA Community
<btn_profile_greytxt_80x15.gif>
Ralf Bokelberg wrote:
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
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
--
: : ) Scott
Helping your grandma on the interweb
at: http://blog.criticalpile.com
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
|
