Closed GijsTimmers closed 9 years ago
Maybe we should replace it by AnimationCommunicator()
I'm not using it, though I think it somehow shows what's possible with the separating of the communicator pattern. I personally see it more as a demonstration of what's possible, a skeleton for another awesome communicator maybe (such as an AnimationCommunicator)... So I won't remove it too quick. Especially since the communicator itself is not the problem. I'm writing a (long) issue on the problem now...
Agreed, closing.
Although the
CursesCommunicator()
was nice to play with, it differs so much from the other Communicators that it is a hassle to keep it up-to-date. Also, it's not crossplatform. I'm thinking of removing it. Thoughts?