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?

Thank you.

My question still standards as to why the modulebase externsion implementation through IPipeAware does not create individual swiffs - just for my education.

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.

Cliff, I am an ardent fan of singlecore, and I continuosly insist my team to go through the first pains of learning and I have to say it is a success story for me. I hope singlecore continuous to benefit from the focus on multicore. I feel singlecore appeals to small apps, and multicore w/pipes as it is now appeals to complex apps and is just harder to sell to developers for small apps.

I may be caused more grief than expected when I asked for accommodating Fabrication. My intention (poorly communicated) is to understand if key features such as reflection and the notion of notification would be extended to pipes to reduce the boiler plate without the need for using fabrication?

Thanks for your explanation and I understand and appreciate your clear direction on change management. PureMvc works.

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

Multicore and Pipes is a great offering, however PureMVC continues to push the 'duanting at first sight' even more with multicore. The Fabrication implementation simplifies this, and should get as much attention as the Multicore. I hope Cliff and all the smart developers move this ahead. 

Thank you.

Cliff, thanks. Just one clarification - as I did not get info on Adobe.

Does the state event 'enter_state' get fired only after all the addChild views are available? I was wondering if I have to listen to events that get originated from the creationComplete of the newly added component the first time, or I can simply use the enter_state and exit_state to co-ordinate per your input.

just to add code context ... a sample below:

//parent code ...
//  state s1 adds component c1.
//    c1 fires a creationComplete to the parent, which in turn fires
//    EVENT_C1_CREATED to inform the mediator
//
//    watch I had to keep a boolean flag as state to track the creation.

<mx:states>
  <mx:State name="s1">
    <mx:AddChild>
      <mx:target>
        <components:C1 id="c1"
           onc1CreatedEvent="_bc1Created = true;
           dispatchEvent(new Event(EVENT_C1_CREATED));"/>

//base state
//As the user may reactivate S1 after initial creation, the mediator needs to know again.
// the boolean flag is checked to re fire the creation event to allow the mediator to do whatever....

<components:B1 id="b1"
   c1SelectedEvent="currentState='customScanInputState';
      (_bc1Created)?dispatchEvent(new Event(EVENT_C1_CREATED)):''"

                     
This is a mess. I hope someone can provide me guidance.

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.

I saw your MainDisplayMediator.as example, and now seem to get the idea. Please see my previous thread, as I would like you to suggest something more appropriate for the usecase.

Also Cliff forgot to mention that the mediator try to access unique notification by accessing a public variable implemented in GenericView, but populared by the ServiceView.

So how can I access a view property before executing listNotificationsInterests? I am assuming the view coupling is after mediator creation, and here it looks like listNotificationsInterests happens before view coupling.

THANKYOU.

Cliff thanks. I understand your info, but I am missing one more thing. So really appreciate your insight.

My use case is simple. Verify a bunch of HTTP services. The request params are prompted using Form. Although the services are different from each other, they also share a common set of parameters. So I implemented a GenericView with a standard form containing the common set of form items and the submit process. Next I extended the GenericView to respective Service#1View, Service#2View etc. Each ServiceView uses addChildAdd to introduce additional form items and overrides the submit process.

Now the ServiceViews are under a ViewStack. So the mediator gets handed the ServiceView Object accordingly. However the mediator does not know which child view was passed, so I simply cast to GenericView to access view attributes in the mediator, and I really only need access to attributes defined in the GenericView.  Now since I don't know the view, I have to assign a generic notification id between the mediator and the model. However I can not support a multi threaded model effectively.

So if Service#1View was invoked,
- I want the mediator to first retrieve the generic model.
- Then mediator will tell generic proxy to notify back using notification "Service#1View".
- Then mediator will kick off model process.
- Model will notify using the "Service#1View" when it has fault or result event.
- Mediator will then update the response area which is inside GenericView.

Explain to me what happens when the same instance of Flex runs Service#1View and Service#2View concurrently. I have to use a unique notification to track them.

What I am saying is I need listNotificationsInterest to be kicked off after the View object is created. While debugging I found that listNotificationInterest is executed as part of the construction phase. Is there a possibility of calling listNotificationInterest out of the event handler coming from the view submit event?

Thanks.

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.