Status update: Feb 15th

[Andrew Hyatt]

The past month I've made some changes to the code and fixed a few
bugs. The big work has been on getting a browser channel
communication setup with the Wave server. This is just been started,
and may be tricky due to issues with the url library and https.

There are now two main tracks of work: getting the wave-reading UI to
be solid, and getting live updates and writes to work.

Here's what needs to happen with the wave-reading UI:

- We need to make use of some wavelet metadata that shows how the
blips should be arranged.
- Wave reading needs to make sense from a buffer management
perspective. Right now if you kill the wave buffer, you don't get
taken back to the wave list buffer. This needs to be more polished.
- More annotations need to be respected, such as underline, italic, etc.
- The blip-rendering code needs to be refactored for cleanliness, and
to not use recursion anymore.

The live updates is what I'm working on now, and once it works we'll
have a channel for read/write communication that will power the rest
of the wave server.

As always, there's a lot of work to be done, so volunteers would be welcome.