Initial commit of EchoTree package.
Added pyedoc comments.
Began work on server to serve echo trees.
First running sample of cherrypy server.
Started with Web server.
Progress in server that both, listens for json tree updates, and serves out the trees via SocketServer/HTML5 server-sent events.
Created client-side html page wordTreeListener.html, which initiates and receives new word trees by interacting with the echo_tree_server.py at the server side.
Added detection of dropped connections. Getting there.
Merge branch 'master' of ssh://kforge.ros.org/robhum/echo_tree
Continued on EchoTree server.
All three servers work: initial serving of a JavaScript to browser clients, submitting a new JSON EchoTree, and pushing submitted EchoTrees to registered clients in browsers.
Not working: clients using the JavaScript to start the event stream. Complaint is inability to connect to server. Yet wget works find: wget mono.stanford.edu:5001 to subscribe to events.
Added HTML documention via epydoc into doc subdir.
Added test for 'socket in use'
Replaced cherrypy3 with tornado in rosdep.yaml. Continued with rewriting the three servers to use WebSocket. Modified JS accordingly. To do: HTTP server bombs.
Safety commit: Just before chaning new-tree submission server from WebSocket to HTTP.
Intermediate commit; still problems\!
Whole mechanism works, except for DB needing to be used in the thread in which is was opened. That's next.
Completed simple tester. Multiple subscribers work now.
Added tester_cli.py, which is command line equivalent to tester_gui.py. Provided so that PyQt4 does not need to be present for testing.
Cleaned up epydoc documentation in doc subdirectory.
Removed the unused src/java_script directory.