Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Proposal: removing CursesCommunicator() #48

Closed
GijsTimmers opened this issue Dec 10, 2014 · 3 comments
Closed

Proposal: removing CursesCommunicator() #48

GijsTimmers opened this issue Dec 10, 2014 · 3 comments

Comments

@GijsTimmers
Copy link
Owner

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?
@GijsTimmers
Copy link
Owner Author

Maybe we should replace it by AnimationCommunicator()

@jovanbulck
Copy link
Collaborator

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...

@jovanbulck jovanbulck mentioned this issue Dec 10, 2014
Closed
@GijsTimmers
Copy link
Owner Author

Agreed, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@GijsTimmers @jovanbulck