Feature suggestion: API for other programs to control TTB

[olliecheng]

Suggestion for feature: implement a background web server on a specified port which exposes a RESTful API which allows for other applications to control TTB (with user permission, of course).

[emmatyping]

Meh, I think this may add too much bloat. I think the next release (after V4) could go this route, but then we will want to decouple the current UI and the core part.

[olliecheng]

It doesn't necessarily have to be a RESTful API (even though that would be easiest to control from within Node.JS or Python), but a programmable interface would be nice. Also, moving priority down to low as there probably isn't much demand for such a feature. Of course, if anyone reading feels such a feature would be useful feel free to tell us :)

[sylveon]

Implementing a named pipe from the hook to a client program would be ideal. This way, we could have diverse client programs, and allow the hook to live without a client running either.

[olliecheng]

I agree with that. (By the way, this should be implemented after #134, as the suggestion would be best done with the listening being done by a hook.) After such an implementation, should we rewrite the client to make use of the new named pipe API?