Thanks for the reply!
Since all the component in the main app does assigned with a unique ID, I prefer this way:

super(viewComponent.id, viewComponent);

now it works.

Curious at how the View add the mediator into observer, I looks at your framework source code and here is the one I found  -->view.as<--

      public function registerMediator( mediator:IMediator ) : void
      {
         // do not allow re-registration (you must to removeMediator fist)
         if ( mediatorMap[ mediator.getMediatorName() ] != null ) return;
         
         // Register the Mediator for retrieval by name
         mediatorMap[ mediator.getMediatorName() ] = mediator;
                                      .................blah blah blah
                         }


Thanks for the fast reply and great works!

Henry

Hi again,
I have soem problem with this: I have two viewComponent:
      <components:AuthenticationStatus id="wAuthenticationStatus" right="0" top="0"/>
      <components:AuthenticationStatus id="wAuthenticationStatus2" right="0" top="100"/>

In my startup command I include like this:
        override public function execute( note:INotification ):void{          
           facade.registerProxy( new UserProxy() );
           /**
          * Get the View Components for the Mediators from the app,
             * which passed a reference to itself on the notification.
             */
             var app:main = note.getBody() as main;
             facade.registerMediator( new ApplicationMediator(app) );
             facade.registerMediator( new AuthenticationMediator(app.wAuthenticationStatus) );
             facade.registerMediator( new AuthenticationMediator(app.wAuthenticationStatus2) );
        }


The mediator like below:
      public override function handleNotification(notification:INotification):void {
         var body:Object = notification.getBody() as Object;
         switch (notification.getName()) {
            case ApplicationFacade.STARTUP:
               showLoginForm();
               break;
            case ApplicationFacade.AUTHENTICATED_SUCCESS:
               var credentials:UserDescriptor = notification.getBody() as UserDescriptor;
               hideLoginForm();
               setUsername( credentials.username );
               
               break;
            case ApplicationFacade.UNAUTHENTICATED_SUCCESS:
               showLoginForm();
               setUsername("");
               _loginForm.reset();
               
               break;
         }
      }

      private function setUsername(username:String):void {
         this.authenticationStatus.currentUsername = username;
         
      }


      private function get authenticationStatus():AuthenticationStatus {
         return this.viewComponent as AuthenticationStatus;
      }



AuthenticationStatus.mxml has a textbox: currectUsername
   <mx:Text x="10" y="16" width="110" textAlign="right" id="currectUsername" color="#FFFFFF"/>




The problem is, on AUTHENTICATED_SUCCESS, only first viewComponent is updated with userID no matter you click on Login button of first or second component.

Aren't both the object listen to the notification since they are the same mediator class? it should by right update both viewComponent.

in startup command,
changing the sequence:
             facade.registerMediator( new AuthenticationMediator(app.wAuthenticationStatus2) );
             facade.registerMediator( new AuthenticationMediator(app.wAuthenticationStatus) );
won't help but it update only 2nd viewcompoent.

Any idea why is it so?

Thanks

Thanks for the reply!
That is really impressive response time 
I am having an evaluation whetehr I need to choose Cairngorm / pureMVC for my coming Flex application. seems that Puremvc is my choice.
Here I need to ask another question:

Can I create multiple instance of view, tied to single mediator?
<custom:button id="button1" top="0" right="0">
<custom:button id="button2" bottom="0" right="0">

both the buttons will dispatch an event so can 1 mediator listen to both of them? If not, any way I can achieve it without rewriting another mediator class?

Hi there,
I have a flex app, which show login panel at beginning, with animation effect. after login, it shows the main app menubar, treeview, working panels, etc.
I put all of these view component within 1 mxml, using some logic to set the visibility for login panels and the nagivation/working  panel.
now I wan to refactor all of these to puremvc framework. any advice on how i can start my work?

I understand that I need to separate some of the viewcomponent into separate mxml and define their own mvc folders with some codes. but what about the animation and state? where to put them together?

any advice will be appreciated. Thanks!

Henry




<mx:Application xmlns:comp="my.customcomponents.*"
   xmlns:mx="http://www.adobe.com/2006/mxml"
   layout="absolute" creationComplete="init()" width="100%" height="100%"
   verticalAlign="middle" horizontalAlign="center">
   <mx:states>
      <mx:State name="showLogin">
         <mx:SetProperty target="{pnlLogin}" name="visible" value="true"/>
         <mx:SetProperty target="{mainApp}" name="visible" value="false"/>
         <mx:SetProperty target="{DBPanel}" name="visible" value="false"/>
         <mx:SetProperty target="{menu}" name="enabled" value="false"/>
      </mx:State>
      <mx:State name="showMainApp">...some states</mx:State>
   </mx:states>
   <mx:transitions>
      <mx:Transition fromState="*" toState="showLogin" >
         <mx:Sequence>
                             /...some transition
   </mx:transitions>
   <mx:Panel id="pnlLogin" width="430" height="224" layout="absolute"
      title="FBI Console - Login Panel" horizontalAlign="center" verticalAlign="middle">
      <mx:Button x="267.5" y="136" label="Login" click="processLogin()"/>
      <mx:TextInput x="163.5" y="45" id="txtUserID" editable="true" enabled="true"
         text="demo"/>
      <mx:TextInput x="163.5" y="90" id="txtPassword" displayAsPassword="true"
         editable="true" enabled="true" text="1234"/>
      <mx:Text x="95.5" y="47" text="User ID : "/>
      <mx:Text x="86.5" y="92" text="Password : "/>
      <mx:Label id="lblLoginStatus" x="86.5" y="138" width="173"  fontFamily="Verdana" fontWeight="bold" color="#0B333C"/>
   </mx:Panel>

   <mx:ApplicationControlBar id="menu" paddingLeft="15" paddingRight="15" dock="true"
      x="0" y="0" width="100%" height="35">
      <mx:MenuBar width="100%" labelField="@label"
         itemClick="itemClickHandler(event);" >
         <mx:XMLList>
            <menuitem label="File">
               <menuitem label="Browser"/>
            </menuitem>
                <menuitem label="CoMa"/>
                <menuitem label="Help" >
                    <menuitem label="About" type="radio" groupName="one"/>
                    <menuitem label="Help" type="radio" groupName="one"/>
                </menuitem>
            </mx:XMLList>
      </mx:MenuBar>
   </mx:ApplicationControlBar>


   <mx:HDividedBox id="mainApp" x="0" y="0" width="100%" height="100%">
      <mx:Panel width="30%" height="100%" layout="absolute">
         <mx:Tree id="tree" width="100%" height="100%" showRoot="false"
            dataProvider="{xmlMap}" itemClick="treeItemClick(event);"
            labelField="@label" iconField="@icon">
         </mx:Tree>
      </mx:Panel>
                        //some others object lies here..

   </mx:HDividedBox>
</mx:Application>

Hi,
Sorry I am still not very clear with the explanation.
Take for example:
the viewcomponent: UserForm.mxml
Is it fixed that the correspond mediator AS filename must have the format like: vcomponent name follow by "Mediator"  => UserFormMediator.as ?
Is it we have to name the mediator follow that way in order for the startup command to "know" what  mediator(s) should be registered in the application facade?
Or the facade registered all mediator under [view] folder?

Hi,
Allow me to post a simple question here but I need to make things clear before dig further.
Take for example, EmployeeAdmin project. I see the EmployeeAdmin.mxml create a facade and run its startup method, which in turn sendnotification "startup".
How does it work that register all mediators with their interest notification?

In the [view] forlder I noticed there are 3 mediators.as. Is it when startup notification sent, all class in view component will be registered automatically?

Thanks

henry