I have used puremvc in flex before, and trying the same in c#. Question is about single window, multiple views using concept of viewstack, and ideally lazy loading.

One approach is the grid and all views created in same co-ordinates. Using the visibility property through puremvc.

Any other better suggestion?

Cliff,

We recently implemented mc version of our single-core application using mx:modules, and are not yet using pipes. In looking at the pipeworks demo, I am confused why the module's (Logger / Prattle) swf don't exist - when the implementation uses modulebase.

If the mediator loads ahead of the view creation to do the framework wiring, do we lose the benefits of independent swf loading and memory management - as I only see one consolidated swf in pipeworks?  I am not clear, just need you to point me to more resources to look at.

Thanks.

I see Fabrication stream on Google. I am wondering why this is not in PureMVC home page?  Thank you.

Although I can have work arounds, I am looking to understand how someone has tackled the re-activation of a state that involes addChild.

The addChild component fires a creationComplete event to get its mediator registered. However I am looking for a clean way of informing the mediator of the reactivation of this child. The creationComplete won't play a role in the reactivation of this child.

Thanks.

As I am using deferred instantiation, I do not see any way around having the mediator listen to state change events and determining when the addchild component is created. 

I have read about the puremvc statemachine, however I am wondering if anyone has a better approach of handling addchild views in puremvc.

Pardon my limited expertise.

In implementing mediator on flex, I realize the listNotificationInterest method is executed during the construction of the mediator. Is there a method available to dynamically modify the notification list after mediator is constructed. I have a generic mediator which supports multiple views, so I want to include a notification in mediator under the event handler scope instead of the construction phase - as the notification value will only be available on creationComplete of the view.

Thank you.