ello,

Just a quick question - in an app using Pipes for dynamic module loading, where do you reckon is the best place to handle the loading of the module (integrating with ModuleManager, listening for progress / setup / ready events etc).

Off the top of my head, it seems like this should go in a Proxy which can handle loading of modules, with each load triggered by a Command. The Proxy can handle the loading of the module, then when loading is complete, a notification is sent out (perhaps with the module's factory in the notification body). Any interested parties can then do what they want with the module once they know it's loaded.

I think this makes more sense than putting it in a Mediator or Command.

I'd appreciate any insight or thoughts.

Cheers!
Toby

Hi there,

After recently getting to grips with PureMVC and building a couple of test apps, I'm diving in to using it for a larger application. It'll be a Flex app with multiple modules (using Pipes), and I've got the structure worked out quite nicely as I'd like it.

In my test apps, I've tended to create a class which purely exists to define all the Notification name constants, so that any class that needs to send a notification, or react to one, can gather the constant name from this one class. I decided not to put them in the ApplicationFacade to keep that class nice and simple. This has been working pretty well for me, but I'm wondering if it's 'Best Practice'?

Obviously, I'm gonna need one of these constant-storing classes per Module, and the fact that I'm using Modules is really irrelevant to my question. I'm interested to know what people have done when building larger apps with the framework - are you tending to keep everything inside ApplicationFacade? Are you creating a class just to store all the constant names? Are you doing something else which I hadn't considered?

Any info would be much appreciated.
Cheers,
toby