True or False? Not good pratice to have import org.puremvc* in Mediators

Though you can retrieve a mediator and manipulate it directly, its best to send notes between them instead to keep unnecessary couplings to a minimum.

However, mediators often need to create other mediators and so may need to be able to instantiate them. For instance, an ApplicationMediator generally takes reciept of the sole lasting reference to the main application view hierarchy. This mediator will then generally 'snap off twigs' of the view tree and hand them to new mediators which it creates and registers. This may happen recursively with those newly registered mediators immediately or at a deferred time registering new mediators for the children of their view components.

That's the scoop on mediator to mediator interaction, however your mediators ar usually all in the same package with each other and so don't need imports to see each other. And that package wouldn't be org.puremvc, but more like com.myapp.view.*

And on the subject of using * for import; irregardless of what framework you use (if any), using the glob is a bad idea. Not because the classes would all be compiled in, they won't, the reason is maintainability. When someone looks at a class the imports tell the story of what the classes actual collaborators are. With globbing, you have no idea unless you inspect all the code. If you are using FlexBuilder/Eclipse, a Ctrl-shift-O will do an 'Organize Imports', sorting them and discarding unused imports. Teach your fingers this immediately. Every time you save a class - always organize imports by rote. Even if you haven't dropped a class or added one.

If you aren't lucky enough to have this feature in your environment, then be diligent about manual organization. Its worth the effort.

-=Cliff>