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 2 3 [4]
46  Announcements and General Discussion / General Discussion / Should notifications always go through a Command on: February 15, 2009, 04:11:59
Should all notifications be registered with a command?  If not when should then vs. when shouldn't they?

Should you only registerCommand's when they are big events like on startup, major changes, or shut downs?

47  Announcements and General Discussion / Architecture / Re: 1000 Sprites /w data. Mediator for each? Memory? on: February 14, 2009, 09:28:02
Cliff would there ever be a need for any reason to add a proxy for each Sprite? So something like this:

facade.registerProxy(new TestNodeProxy( n.name+"Proxy" ) );
facade.registerMediator( new TestNodeMediator( n ) );

Given n is a type of Object (Sprite, MC, etc...)
48  Announcements and General Discussion / Architecture / Re: 1000 Sprites /w data. Mediator for each? Memory? on: February 13, 2009, 03:36:20
Won't that make the the performance worse?  I would then need to keep track of the nodes and edges in a Dictionary and do a lookup each time a get an event. So say a mouseover happens and I want to the sprite to display text and turn colors and increase size by 25%.  And maybe a click I want it to make the textfield editable.  I would then need to do a lookup for the node and then a lookup for the textfield in the proxy and make all the changes there.

Maybe a better question than my original is would there ever be a need to have one mediator and proxy for each 1000 nodes/edges. What would that get me that using only one med. and one proxy for all nodes/edges wouldn't?

49  Announcements and General Discussion / Architecture / 1000 Sprites /w data. Mediator for each? Memory? on: February 13, 2009, 12:41:55
I am building my first PureMVC based project and wondering which would be the best way to go.

My app can have up to 1000 sprites, think node/edge (tree structure), and I am thinking of giving each node and edge its own mediator and proxy.  I don't have to do this as I have a collection item that keeps track of each node and edge group ( so 500 in each), which contains functions to manipulate each node/edge.  But, it would make things a little more flexible if I can handle some mouse related events on each node and edge directly. 

So my question is? Is there any issues with memory usage with giving each node/edge (up to 1000 total) their own proxy and mediator?  Keep in mind my app will already be a memory/cpu hog because of all the sprites.

Or should I go with just a mediator and proxy for the container that holds all 1000 sprites?

50  Announcements and General Discussion / Architecture / To multicore or not to multicore? on: February 03, 2009, 04:50:11
I am starting a PureMVC Flex app and wondered if anyone can lend some puremvc experience upon me.

I have an app that has two modes design and view mode. I am trying to go the easiest path here so I am not sure if Modules would be a better way to go or would it be better to go another way. 

The issue is I have mouse click events and keyboard events that I listen for and their functions are completely different in each mode. So would modules be easiest or do something like remove Proxies and Mediators be the best route?

Pages: 1 2 3 [4]