he's twittered on it in the last 6 months...

Certainly not holding my breath though

That is pretty cool. How was it developing for the facebook? I like how the 'chips' system is there to generate revenue. Has it been profitable?

PureMVC is rock solid, production tested, has many utilities/demos/extensions, is fully unit tested, follows best practices, is true to the patterns it implements, and works really well over all.

That is why I use it.

Orchid UI is from the same cat that was working on Saffron UML, no? He's all but dropped off the face of the planet. My understanding is that he got so wrapped up in Orchid that he was rewriting Saffron to use it. The screens of Saffron were so sweet, it should be nice when it finally sees the light of day.

http://www.levelofindustry.com/

His website has been down for months and months (damn, almost a year!).

It might also be helpful to run a monitor like Charles to see what is coming back from the service.

Also, I've found that I have to create an instance of my VOs in the root of my application:

<vo:MyVO />

or AMF doesn't want to recognize the typed object. Casting an object as will return null if the type isn't correct, so I'd assume that is the problem. Something about the signature doesn't match.

http://www.as3dp.com/

Actionscript 3 Design Patterns is an awesome text also. It isn't a replacement for the GoF book, which is THE foundation, but it is a nice supplement and puts it in context.

It makes sense now that I think about, but makes me sad because everything I have written violates this principle

Now where did I put my "can't talk refactoring" hat...

Thanks, really apreciate.

One more doubt on this.
Is it okey to declare global variable in ApplicationFacade
and  get the data through proxy and use facade to get the global variable.

ApplicationFacade

{     public var myGlobalVariable;    ApplicationFacade( ){      var myProxy:MyProxy = facade.retriveProxy(MyProxy.NAME) as MyProxy;      myGlobalVariable =  myProxy.retrieveGlobalVariables();    } }

[/color]
and then access the global variable using facade

Thanks,
Mansoor

There is 100% no reason to do this as any mediator, command, or proxy can access the proxy by calling facade.retrieveProxy(MyProxy.NAME)

I recommend removing 'global variable' from your vocabulary in terms of PureMVC applications.

Proxies shouldn't access ApplicationFacade constants?

I would access the XML in a proxy and then access that proxy in your mediators, commands and other proxies.

I use mind maps for planning almost any major project. MindJet MindManager is my favorite commercial solution, but Freemind is a decent OSS tool.

Thanks for the feedback! I took the same road like Joel proposed (after making sure the mediator name is unique through createUID). I don't understand however that (Pure)MVC doesn't have support for something essential like this out of the box 

My guess is that the framework is supposed to be 'as simple as possible, but no simpler' and this sort of solution is one that will vary from project to project. Using the Notification body and/or type parameters is effective for this sort of thing, so really it does support it out of box.

If you have a good way to plumb something up, you might consider writing a utility to do so. I'd love to check it out. I'm running through solutions in my head, but I get stuck at the way I've always done it (as described in my other post).

Cheers

You'll have to pass around some sort of identifier (the mediators name?), so I guess that is a yes to your plumbing question.

@Joel, Proxies (denizens of the Model region) are not conceptually a good place to store view components.

-=Cliff>

I assumed (didn't read closely enough) that an ArrayCollection would be thumbnail value objects and not the components/renderers.

Thanks for the reply. I got the idea of unique id + NAME. What about the notification then? To my understanding, the current notification mechanism of puremvc is at "class" level, instead of instance level. Any good idea to make it work at instance level?

:

case NotificationSender.IMPORTANT_NOTIFICATION:
if(notification.getBody().uniqueIdentifier == this.aValueObject.uniqueProperty)
{
     doStuff();
}
So notifications are declared at the class level, but you can check against your instance to see if it needs to react.