Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought

Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Show Posts

* | |

  Show Posts
Pages: [1]
1  Announcements and General Discussion / General Discussion / Re: PureMVC Vs parsley on: April 15, 2011, 01:24:01
Thank you Cliff.

2  Announcements and General Discussion / General Discussion / Re: PureMVC Vs parsley on: April 13, 2011, 09:46:34

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

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.

Yes, my commands are in the concrete Facade's initializeController method, but this is growing over time. Any suggestions here...thanks
3  Announcements and General Discussion / General Discussion / Standards for removing event listeners and unwatch bindings on: April 12, 2011, 01:30:22
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!
4  Announcements and General Discussion / General Discussion / PureMVC Vs parsley on: April 12, 2011, 01:25:29
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.

Pages: [1]