Cool addition with the public var notifications in the facade. If this was added to the framework it would remove the need to create concrete facades in many cases. Also the protected variable facade provided by the Notifier class would always allow access to all notifications. Thus also the dynamic adding and removing of commands could be solved that way.

@hasanotuome:

Following your approach, how are you accessing the "notes" variable of the ApplicationFacade from within Mediators, Proxies and Commands?

Mediators, Proxies and Commands have the inherited instance-variable facade, a reference to the Facade supertype, but it is typed to IFacade, so, for example, we cannot use facade.notes.login.LOGOUT to get at the constant (notification name).

We can use ApplicationFacade.getInstance().notes.login.LOGOUT, but of course, we have to import our concrete ApplicationFacade class into each actor where needed.

What's your approach here?

Thanks,
jf

I've use your solution in my new application to define my notifications constants, but there was a problem because the concrete facade wasn't already accessible from my different mediators and proxies while registrating them, the facade returned null, so it was impossible to access my notifications vars.

So, i had to create a getter in my differents mediators and proxies to access the facade like this :

protected function get _facade():LoginModuleFacade
{
if ( multitonKey == null ) throw Error( MULTITON_MSG );
return Facade.getInstance( multitonKey ) as LoginModuleFacade;
}

don't know if it's the right way to do this…

Regards,
Ódýr Vefhýsing

This post was mentioned on Twitter by nebutch: My coworker at Almer/Blank wrote up a good article on PMVC notification organization. http://bit.ly/4EhPue…

If you use public const vs public static const in your Notification classes and then create instances of your Notification classes in your Facade, you won't need additional imports in your Mediators, Proxies or Commands as they will still be available via your concrete Facade.

You could further expand this approach by wrapping all your Notification classes in a Notifications class and letting this be the intermediary between your concrete Facade and Notifications.

package com.project
{
	import com.project.controller.notifications.Notifications;
 
	import org.puremvc.as3.patterns.facade.Facade;
 
	public var notes:Notifications;
 
	public class ProjectFacade extends Facade
	{
		public function ProjectFacade()
		{
			super();
		}
 
		static public function getInstance():ProjectFacade
		{
			if (!instance) instance = new ProjectFacade();
 
			return instance;
		}
 
		override protected function initializeController():void
		{
			super.initializeController();
 
			notes = new Notifications( this );
		}
	}
}

That's your modified Facade and here's the Notifications wrapper class:

package com.project.controller.notifications
{
	import org.puremvc.as3.interfaces.IFacade;
 
	public class Notifications
	{
		public var application:ApplicationNotifications;
		public var login:LoginNotications;
 
		public function Notifications( facade:IFacade )
		{
			application = new ApplicationNotifications( facade );
			login = new LoginNotifications( facade );
			// etc, etc...
		}
	}
}

And finally, your slightly modified Notification class:

package com.project.controller.notifications
{
	import com.project.controller.commands.LoginCommand;
	import com.project.controller.commands.LogoutCommand;
 
	import org.puremvc.as3.interfaces.IFacade;
 
	public class LoginNotifications
	{
		public const LOGIN:String = "LOGIN_NOTIFICATION";
 
		public const LOGOUT:String = "LOGOUT_NOTIFICATION";
 
		public function LoginNotifications( facade:IFacade )
		{
			facade.registerCommand( LOGIN, LoginCommand );
			facade.registerCommand( LOGOUT, LogoutCommand );
		}
	}
}

Each Notification class would still handle its command registration process and you would gain access to your Notifications using the notes attribute in your concrete Facade. Hope this helps…

Don't get me wrong, I actually really like the idea of creating locial groups notifications and it certainly outweighs the imports issue. I'll probably try this on my next project. Thanks for sharing!