Decouple From Chatterbox #87
Comments
ghost
assigned
photofroggy
pushed a commit
that referenced
this issue
Sep 28, 2013
…ain functions and recode chatterbox to accommodate for changes to the API. #87.
photofroggy
pushed a commit
that referenced
this issue
Sep 28, 2013
photofroggy
pushed a commit
that referenced
this issue
Sep 28, 2013
photofroggy
pushed a commit
that referenced
this issue
Nov 3, 2013
… added log event to wsc and chatterbox. used in one or two places. need to make sure separation is clean and extensions use updated stuff. need to rename some stuff. #87
photofroggy
pushed a commit
that referenced
this issue
Nov 3, 2013
… extensions to new setup. woo. #87
photofroggy
pushed a commit
that referenced
this issue
Nov 6, 2013
…appen properly. Also need to make a UI for it in Chatterbox. #87
photofroggy
pushed a commit
that referenced
this issue
Nov 6, 2013
…erly without certain UI stuff working. could make ignores work on a lower level in the client. maybe. woo. #87
photofroggy
pushed a commit
that referenced
this issue
Nov 6, 2013
photofroggy
pushed a commit
that referenced
this issue
Nov 6, 2013
photofroggy
pushed a commit
that referenced
this issue
Dec 1, 2013
photofroggy
pushed a commit
that referenced
this issue
Dec 1, 2013
…te to have them in the core when these are commands that work with the GUI and not the client itself. #87
photofroggy
pushed a commit
that referenced
this issue
Dec 3, 2013
…iate. bug fixes here and there. #87
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Must decouple wsc and chatterbox.
wsc is intended to simply be a client. Chatterbox is a UI, but not an integral part of the client. So, all references to Chatterbox need to be removed from wsc.
Should also probably create separate repository for Chatterbox.
The text was updated successfully, but these errors were encountered: