Is there such a thing as a manager design pattern that controls how different entities interact?
This is for a project for which the Environment, EnvironmentListener
, and Entity classes have been predefined by our professor.
The static class, Environment
, has a single EnvironmentListener
interface that has a nextAction()
method it just continuously calls kind of like a main loop in a game and because it is for a design patterns class, i can't simply change the code.
I need to allow entities to be dragged, dropped, animated, etc. and thought i would do that using different controllers.
I've been wondering if it was a good idea to make a controller manager which would implement EnvironmentListener
and if a pattern like that existed.
The controller manager would simply iterate through a list of controllers and use their call function.
Design patterns are not meant for project development. Design patterns are meant for common problem-solving. Whenever there is a need, you have to implement a suitable pattern to avoid such problems in the future.
Sounds like you're after the mediator pattern - which can be thought of as a 'manager' of the objects that it deals with.
In many systems, a manager is also a facade for a sub-system, and in that scenario it is more of a facade design pattern.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With