Thanks for your reply!

I have developed several video players myself in the past, ranging from simple to more complex players that integrate an advertising model.  I also have a client that is interested in a "Media" player (video, audio, image, swf slideshow), that could provide the functionality that OSMF has set out to accomplish.  So, I do see a need for this type of player.  However, I may not be as knowledgeable on the inner-workings of the OSMF framework as yourself, and would love if you could elaborate more.

I can't see Adobe abandoning this project anytime soon, and it would seem wise to embrace this new framework than reject these efforts to create a decent standard.

Has anyone in the PureMVC community integrated the OSMF platform into PureMVC yet?  Has anyone else looked into it?

Nope, you're right!  Thanks for straightening me out

sure.  The creationComplete event is not fired by the time the mediator is registered, so I should be able to listen to it.  That is the point of this post.  For whatever reason, I can't listen to that event being fired ... even though I add an eventlistener before the event is fired.

I'm 100% sure that the reactTo is meant to work with Flex events, or any events for that matter.

I really wish so!   The only logical answer I can come up with to support my conclusion, is found in the org.puremvc.as3.multicore.utilities.fabrication.vo.Reaction class on line 94, with this function here:

:

public function fulfil(event:Event):void {
handler(event);
}
I understand that FlexEvent is a sub class of Event, but MouseEvent also extends Event ... and works just fine.  So, I'm not sure if that function above has anything to do with it (probably not).

Hmmm, I'm not entirely sure that this is correct, because in my Application file, I listen for creationComplete and trace it out, and in my ApplicationMediator I trace the mediator out when it registers ... and low and behold, ApplicationMediator gets registered first, and then the creationComplete event is traced.

Is it possible that you can't listen for FlexEvent calls with reactions?  I solved my small problem by just listening for the Event.ADDED_TO_STAGE in my Mediator, which I used as a reaction (reactToApplicationAddedToStage).

I understand what you guys are saying, but it still doesn't make sense to me.

Can anyone confirm that they have this working?  I'm trying to listen to a creationComplete from my application with my Mediator, however it does not seem to get called.  However, I have a handler that listens for resize that works just fine.

so to cap off:

reactToApplicationResize( e:Event ) - works just fine;
reactToApplicationCreationComplete( e:FlexEvent ) - does not work


any ideas?

Hmmm.  Well there are different types of fullscreen states in my app.  The one I was mentioning was when on a landing page and transitioning form the normal screen to fullscreen, it adds and removes components.  When say a video component is viewed, it has small, normal, and fullscreen states.

Cliff, thanks for your reply.

So something like a fullscreen state, would it fall under a view or application state?

Hey Jason,

Thanks for the reply, and great analogy.  I believe I remember seeing you post in the Fabrication forum, and I'm wondering if you have tried loading modules into a module, into a module.  How have you found this to work out with Fabrication?

From my reading, it looks like this utility is more for application states ... than view states.  Is there a proper way to handle view states with the State class?

When is the best time to use another Application container, and when is the best time to use Modules?  If I have an Application that has 5 main categories, should each category become a module, or another Application container?  And if I use Module, can I load multiple modules inside modules ... inside modules?  Is it possible to have 'n' number of modules loaded inside each other?

Just wondering what the best practice would be ..

  My apologies, I fixed this a week ago or so, but never replied back.  It was a stupid mistake on my part.  I was registering this proxy with a name closely related to another proxy, and I just overlooked it.

I'm just this question drives the admins mad.  I just figured it out.  It was a typo. Awful eh?  I was extending my proxy class, and I wasn't passing the NAME variable through properly.  Man alive.  Thank you for coping with me.

Hi, I have a Shell app that loads in a module, and then a command inside that module that registers a few proxies and a few mediators inside.  I have the following code:

:

public class LocationStepMediator extends BaseStepMediator
{
public static const NAME:String = "LocationStepMediator";

public function LocationStepMediator()
{
super( NAME );
}

override public function onRegister():void
{
var _proxy:LocationStepProxy = facade.retrieveProxy( LocationStepProxy.NAME ) as LocationStepProxy;
trace( _proxy );
}

}

but my proxy is returning null.  Why would this be?  How do I grab the correct facade instance?  I've loaded my proxy before mediator ... surely this should work?  I feel like it's something simple ..