Page 'redirect' in Mediator or Command?

[jlahr]

If I have a LoginFormMediator that listens for a LOGIN_SUCESSFUL notification from a remote proxy, should I load the homepage.swf  in the LoginFormMediator's notificationHandler? Or, in the interest of code reuse, create a Redirect command that handles the loading of external SWFs and pass it whatever it needs?

Is this something the PureMVC has a philosophy on or am I starting to get too implementation-specific?

Thanks.

[jlahr]

Thinking more about this, I'm tending towards handling this in a StageMediator (which I'm just now starting to see purpose of) because it's dealing with the entire stage as a View Component rather than just a subsection such as a LoginForm.

Even still, I'm not sure if the StageMediator should manage redirects over a Command.

[hesten]

I don't think you would want to handle any loading of swf files in any mediator. That should probably be handled by a view component.

Mediators shouldn't contain logic as such, except as a "filter" on notifications, that tells some view component what to do upon that specific notification.

[jlahr]

I feel like a View Component would be a bad choice because, in my understanding, they are to have the least amount of logic of any component in the framework. They just package data and hand it of the Mediator.

I feel like a single mediator that did nothing but listen for redirect notifications and accessed the stage accordingly seems like the way to go.

[hesten]

I'm certainly no PureMVC expert, but I do think that Cliff would agree that view components can have lots of logic. A Mediator is just the way a view component has access to the system without actually knowing about the system.

I the case of loading a swf that most likely contain some visual presentation of data(?), I would usually use some container as a view component, and have that handle the loading and error handling. The mediator could pass data to this view component and that would know how to present that data.

(If the swf contains fonts I would normally load it from a proxy in a startup sequence)

[puremvc]

View components should encapsulate their own behaviors and this can cause them to be more complex than you might. Consider a map component might be created for resale or distribution. It might have quite a lot of logic in it that causes it to do awesome things with the map data you give it. In order for it to remain portable, it should encapsulate its behaviors, not have them controlled from code in the mediator. This will allow the component to be easily adapted to the PureMVC system or any other system. If you rely on the mediator to do the magic, then you tie the component to the PureMVC framework.

-=Cliff>

[jlahr]

In this case, the View Component is solely responsible for loading SWFs according to user input and application state so it needs to listen to notifications coming from any number of cores. I figure it doesn't make sense to put notification handling in the View Component since that's what the mediator is good at. So I have a mediator that listens for any LOAD_X notifications and calls the the View Component's loadPage(X) method, which in turns loads a new SWF and a new core.

Even though my View Component relies too heavily on its mediator to tell it what to load, I feel like the component itself is a pretty reusable piece of code in that just loads whatever SWF the mediator passes it.

I'm still developing this so I can't say if it'll work or not. This is just my interpretation on how to implement a Shell core that will allow me to load SWFs on demand.