Thank you Cliff.

Meg

Cliff,

Thanks for your response. I have more follow up questions:


1)
I am doing the following when I register my mediator:

facade.registerMediator(new MyMediator(myView));

and say the following to retrieve it...
myMediator = MyMediator(facade.retrieveMediator(MyMediator.NAME));

Now I want to use the existing view and mediator by creating another instance of it, how do I handle this.

2)
Yes, my commands are in the concrete Facade's initializeController method, but this is growing over time. Any suggestions here...thanks

I would like to know the inbuilt standards in puremvc to remove event listeners and unwatch the binding on all mediators, proxies and views which are not going to be in use any more coz of switch of views in the app.

Who should initiate the remove event listeners - obviously the event which switches the view. But where should this code sit... in a mediator?

There are multiple mediators involved and should we call a method removeEventListeners on all these mediators, which inturn should remove event listeners on their respective views and proxies.

Help appreciated. Thanks!

We currently use PureMVC for our flex app. I am comparing PureMVC and Parsley at the moment. Any thoughts?

Also, I am facing an issue where I want to re-use my view and mediator. Should I go about inherting my mediator or creating another intsance of the same mediator by injecting a different name for it? If so, I will have branch my code in every function to check what name it is to make tweaks to code, if any.

Also, as our app is growing I am registering new commands, mediators and proxies, hereby making my startup command really big...any thoughts on this.

Help is appreciated.

Meg