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 / Architecture / Re: Managing multiple windows with pure MVC. on: February 08, 2012, 07:53:18
@ PureMVC

I got another solution

As each window has children link A>>B>>C>>D say I use unique identifier for this branch so that I can use say parent ID as identifier for all elements in  A,B,C,D because of this if child want to update parent there is no need to send event .But just notification .This will not affect another window as all mediator who are checking identifier has diff identifier of that window :)
2  Announcements and General Discussion / Architecture / Re: Managing multiple windows with pure MVC. on: February 08, 2012, 02:20:59
@puremvc

if my project has such up to 4 level children structure should I support multiple windows .

My each window as structure of A >> B >> C >> D .Due to this depth code is becoming complex to manage identifiers for mediators.


Because it is becoming very complex and code seems to be unmanageable .
Can you give advice on this ?

Even though I have made approach as you suggested


For each notification send identifier and returned that back using async token .For each action in D I have to bubble that up to C and if C refreshed I have to bubble up to B and so on ....
Such events are becoming so much that .....it is needing complete refracting of notifications and existing code in
command , proxy and mediator , view .

CAN YOU GIVE ADVICE THAT WILL IT BE BETTER TO KEEP THIS APPLICATION SINGLE WINDOW SUPPORTED ?
PLEASE HELP ME IN THIS CASE .
3  Announcements and General Discussion / Architecture / Re: Managing multiple windows with pure MVC. on: February 07, 2012, 10:02:03
If i have to do communication with A view from C (UPDATE A's properties from actions of C here B's state is not affected .) will it go through B or directly to A view ?

if directly to A then A should have handle of Object of C to register event on it  .And if C is created when needed ,  in that case C is not available to A when A is created :(
4  Announcements and General Discussion / Getting Started / Re: Proxy notification for multiple mediators on: February 07, 2012, 09:51:35
You have given simple situation where notification screen A sends notification and updates screen A only .
What in case where A updates another screen ????????????
5  Announcements and General Discussion / Architecture / Re: Managing multiple windows with pure MVC. on: February 07, 2012, 09:28:12
Thanks Cliff for reply .

But in my case situation is quite nasty .I browsed your replies in this forum for this .

My situation -
First I have multiple windows/views  in that window say A has child B and  B has child C (A--> B --> C --->  depth May increase in future :( ).Child of B , which is C  is created when action is called on it from B.

Say there are some buttons on C because of which B need refrsh .

Now From you forum I get message that A is parent of B ,C so if C need to refresh B then it should fire event which A will listen and refresh B through its mediator as it has handle to its child B . am I right here
If I have to do conversation between children B and C I have to go through parent A ??
Another question is how to register event for C in mediator of  A because C is created when it is needed means when someone clicks button on B .

Any elegant clean solution for this where I have multiple windows and depth of child more than 3 .?


6  Announcements and General Discussion / Architecture / Managing multiple windows with pure MVC. on: February 07, 2012, 07:01:41
In my application there are multiple screens which can be  minimized like in windows desktop. Now each has different instances of mediator which have same notification. So if I do changes in one screen say press some button >> which sends some command >> to proxy >>then proxy sends notifications to mediator.

But as multiple screens are active there it is showing changes in all screens as they are notified too by proxies .

How to make sure that proxy calls to particular view component (mediator ) and not for all live instances of mediators ?
Pages: [1]