Manages the different instances of the application, like the Scheduler, the PluginManager, the PullManager, GraphManager; Listens for events from these instances and executes the correct actions for those events, this way the components behind Mapper don't need to know about the others, so it should be easy for anyone to change any of those classes without affecting the entire solution.
The most dependent instance that goes beyond Mapper is GraphManager, because it has some important objects you want to access from MapApplet like the VisualizationViewer, because of that you have access to VisualizationViewer, locate a host, clear the selected hosts, and some other GraphManager methods, but you don't have direct access to it.
If you want from MapApplet to execute an action in PullManager you could access PullManager directly using the getPullManager function, this might change in the future. (sorry kinda lack of time to do this the right way)
@author Sergio Guzmán Lorz
|
|
|
|