thanks~

Be sure not to do your module loading on a transient object or with a IModuleInfo local variable.

Thank you very much , kirs~
But what's "thetransient object" or "IModuleInfo local variable" means?
Does it mean like: var loader:ModuleLoader?
Could you give me an example?

And I found the cause is the Web Browser, when I use safair or firfox, it doesn't work, but when I use IE, it worked. I'm confused @_@

mani.

Hi, guys~

I have completed explain the lib of the pipes version of the mortgage app demo which at: http://www.joshuaostrom.com/demos/mortgagepipes/.

But the demo has a little bug, for example, when you click Load Module to load Acme Quick Quote first time, it would not show it, you have to click it again.

I want to fix it, but I find a boring bug with Flex Builder plugs in Eclipse, everytime I update the code, if I debug it immediately, it doesn't change. I have to wait a moment or restart Eclipse. My browser is Safair.

Anyway, I'm a little tired and loney, because no one study this around me. So if you want to get it and study it, just let me know. I'll study Flex for a long time. I hope would be your friend on the way to study Flex~

My email: shineandsky@gmail.com    MSN:shineandsky@gamil.com

mani.

BTW, PipeWorks does use modules, they just aren't dynamically loaded.

-=Cliff>

Thanks for your reply, cliff, I have some idea about that

Hello, nameless hero~

I found a pipes version of the mortgage app at http://www.joshuaostrom.com/demos/mortgagepipes/.
It seems better than the PipeWorks demo, because it use dynamic modules.

And there are other mortgage app, but it doesn't use pipes-----http://dluminosity.com/demos/modules/MortgageApp.html

Both of them implement the same function, and the second demo use DynamicModules.swc, and publish it in the source of it.
But the first demo doesn't publish its lib, anybody know how to get it?

PS:Cliff said he will publish a demo with dynamic modules app, is that like the first one?

Thanks for your time~~
mani.

Thank you~~
It's different as I download before.
I just have a test and it works too, I'm going to check it out~
I'm sorry that I don't run it before ask, I'll never make this mistake 

mani.

Thank you very mush ,Ramanuja~
It works~

Thank you very much, ramanuja

mani.

 
Thank you all the same,  I wish you good health
I'll study it as hard as possible, and then I hope I could do something for that

 :)Hello,great Cliff, I just found your post in the PipeWorks- a PureMVC AS3 MultiCore Demo as follow:

Soon I will introduce a loader utility.

-=Cliff>

So, could you tell me how long it may be?
Thanks for you time~~

Endless thanks~~

Hello, nameless hero, thanks for your time to have a look~     
It's a section code of Facade.as, when it register Mediator, it judge whether (view != null),
but when it register Command and Proxy, it doesn't check.
Is that wrong?

public function registerCommand(noteName:String, commandClassRef:Class):void
      {
         controller.registerCommand(noteName, commandClassRef);
      }
      
      public function registerMediator(mediator:IMediator):void
      {
         if(view != null) view.registerMediator(mediator);
      }
      
      public function registerProxy(proxy:IProxy):void
      {
         model.registerProxy(proxy);
      }

Best regards~
mani.

If not, what's the value of normal PureMVC exists?
The multicorePureMVC could do what normal PureMVC do.
Is multicorePureMVC for complex project, normal PureMVC for simple project?

Thanks for your time~
mani.

I got it~
Thank you , creynders

Hello, nameless hero~
I encountered three problem about Notification of PureMVC, please have a look, Thanks for your time~

public function sendNotification( notificationName:String, body:Object=null, type:String=null ):void
      {
         notifyObservers( new Notification( notificationName, body, type ) );
      }

It's a method of Facade, and there will new a Notfication() instance when Facade call sendNotification each time.
Q1:Why don't make Notification to be singleton instance, as this:

//The method of Notification to configure Notification
public function setNotification(name:String, body:Object=null, type:String=null):INotification
      {
         this.name = name;
         this.body = body;
         this.type = type;
         return this;
      }

//some code section of Facade.
private var _notification:Notification = Notification.getInstance();
public function sendNotification( notificationName:String, body:Object=null, type:String=null ):void
      {
         notifyObservers( _notification.setNotification(notificationName, body, type));
      }

public function notifyObservers(note:INotification):void
      {
         if(view != null) view.notifyObservers(note);
      }

then goto the method notifyObservers of View:

public function notifyObservers(notification:INotification):void
      {
         if(observerMap[notification.getName()] != null){
            var observers:Array = observerMap[notification.getName()] as Array;
            for(var i:Number=0; i<observers.length; i++){
               var observer:IObserver = observers as IObserver;
               observer.notifyObserver(notification);
            }
         }
      }

and then goto the mothod notifyObserver of Observer:
Q2: what's mean of [this.getNotifyMethod().apply(this.getNotifyContext(),[notification])], I feel a bit  dizzy~
I think it means

public function notifyObserver(notification:INotification):void
      {
         //thisArg:* - The object to which the function is applied.
         //argArray:* - An array whose elements are passed to the function as parameters.
         this.getNotifyMethod().apply(this.getNotifyContext(),[notification]);
      }

this is a common method in ApplicationFacade:

public function startup(app:Object):void
       {
          sendNotification( STARTUP, app );   
       }

Q3:Anybody could explain the Notification's inner chain of responsibility mechanism?
In my opinion:
First, Application call sendNotfication(notificationName:String, body:Object=null, type:String=null);
then, inner view call notifyObservers(note:INotification);
then, check out observerMap(In registerMediator method, according to mediator.listNotificationInterests() to registerObserver,
                                           then add element into observersMap),to see if the notification exists, and call notifyObserver.

if(observerMap[notification.getName()] != null){
            var observers:Array = observerMap[notification.getName()] as Array;
            for(var i:Number=0; i<observers.length; i++){
               var observer:IObserver = observers as IObserver;
               observer.notifyObserver(notification);
            }
         }

then, .... I don't know how to say, the point is the mean of {this.getNotifyMethod().apply(this.getNotifyContext(),[notification])}, how it works, and then what happened?

Best regards~~
mani.