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 / How do people handle command class pollution? on: March 11, 2008, 08:51:43
I was just wondering how other people working on large applications deal with the class pollution from having tons of small command classes?

Basically we don't want to be accessing proxies from mediators and would rather have all of the logic done in commands, otherwise it really dilutes the purpose of even having commands imo, I would rather deal with centralized logic.

Now saying that, how do you handle having 100s, if not 1000s of command classes in your application?  Do you try to cut them down to 10-50 core commands and then use the "type" in the command and switch off that?  I have tried this but it couples the mediator with commands a little as you have to know the type you are firing, it can no longer just be a basic registration.

I would love to hear how others solve this issue.
2  Announcements and General Discussion / Architecture / Question about multiple instances of a component. on: February 26, 2008, 02:11:40
I am using PureMVC and I have some components (with mediators/proxies) that I would like to have multiple instances of at once but i am unsure how to do this.  I have not seen any examples of doing this in PureMVC as all components in examples are concrete single instances.

EDIT: Just to clarify I want to have multiple instances of the same View component, as I understand you can have multiple different views and a single mediator.

So basically I have:

[Component A ]
[ textbox        ]
[ textbox        ]
[ datagrid       ]

and also Proxy A and Mediator A that takes Component A as the argument in the constructor.  The issue is that I need many Component A's active in the application at any one time.  Obviously following any of the examples and best use cases the view is just duplicated in every instance as they share the same mediator/proxy.

Pages: [1]