added waiting for server message
show waiting for server when we have not received a server update recently
working on closing the websocket connection gracefully
adding and removing connections only removes or redraws what is necessary rather than redrawing everything. when you are working on this make sure you understand exactly how objects are being copied or compared. i think underscore creates a copy of the .connections array every time something is removed, but this is OK because it is a shallow copy that does not change the underlying objects used, so angular thinks of those elements as not having changed and does not make connections re-create themselves
ok so i think adding and removing connections and syncing them with the server works well now. made the disconnect_on_client function more efficient but probably too complicated since there likely will never be that many connections for it to actually matter
reorganizing comments
connections have to check if jsplumb is ready before rendering themselves
commented code, minor reformatting
refactored tokenize_connection and inverse into utility functions
making it easier to switch to being on the Galileo
fixing merge conflicts
refactored server communication into its own function
refactored slightly
slightly refactored
when the server is slow or disconnected or we have not gotten data yet, show the loading screen
when we fail to connect to the websocket back end server, try again
added comment
when we have not gotten a message from the server in a long time, we trigger the slowness callback
commenting
refactored slightly