It is best practice to create a Mediator for every display item/button?

For example, let's say I am creating a music player. Should I create a mediator for the play button, another one for the progress/scrubber bar, another one for the volume button, and so on?

thanks. that helps a lot.

I'm new to PureMVC, so i want to double check if what I am planning on doing is considered best practice or if there is a better way.

I have a Startup Command that registers a proxy. The proxy takes awhile to get its info, which is needed to start the application. In the meantime, nothing can be done until this info is returned, so there are no other proxies, mediators, etc. Currently, I have the startup Command add an event listener to the proxy and wait until the proxy indicates that the info has been returned. When the info is returned, then  the startup command registers the rest of the start up proxies and mediators that use this initial data.

The startup command is only called once.

Is this an okay practice? Is there a better way to go about this?

How can I get my facade instance directly to listen to a notification?

Does anyone know if there is a walk through on how to implement the StateMachine into your PureMVC framework? The "StopWatch" demo doesn't count as it simply allows you to download the source code. What I'm looking for is a step-by-step description of how to insert the StateMachine code into a PureMVC implementation.

Nevermind, I found it here...
http://puremvc.org/pages/docs/AS3/standard/framework_asdoc/

This site takes a bit to get used to in order to find what you're looking for.

Is there a page on this or another site where the framework's classes are documented in ASDoc or Adobe livedocs style?

For example:
http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/