I understand that. My question is, why not have a mediator class such as SingletonMediator subclassing v 1.6's Mediator which SingletonMediator  would work for the majority of the cases and know its name like, for example, proxies do; having the name getter with the name set by a constructor?

in this case, would it make sense to subclass the org.puremvc.patterns.mediator.Mediator into something like SingletonMediator which would always know its name to avoid this kind of boilerplate found in each concrete today's Mediator:

:

        override public function getMediatorName():String  {
            return EmployeeDetailMediator.NAME;
        }

or is there a need of this boilerplate code at all? In the debugger you can see a class name of an object...

thanks, I got lost in the navigation indeed, now got the code I was looking for 

The only 2 things that appear downloadable to me are the framework itself and the test code. The demos don't work and I don't see how I can download the code. Am I missing something or all this is as intended?