On Sun, Sep 5, 2010 at 1:07 PM, dougx <[email protected]> wrote: > From the start the reasons Fed1 wasn't really usable in the real world > were: > > 1) No web gui (now we have splash, although it is read only..)
The current plan is to make the simple web client usable & pretty instead of enhancing splash. If anyone's interested in taking a stab at cleaning up the look & feel of the simple web client, we'd love some help :) In particular, we need a login page, a better looking inbox view, and for the whole thing not to look like programmer art. There's a bunch of new wave rendering code that never made it live before thats being re-tooled to work with fedone. So, stay away from the code that renders the actual blips for now. > 2) No persistence (yay, mongo db) This should be working real-soon-now. Its stalled behind some updates to fedone's data model. (Fedone is being modified to use the same data structures used in google's production servers [1]). That will add a bunch more metadata to the data model (last modified time on blips, blip contributors, unread counts, etc). When thats done, I want to take a stab at fixing the websocket-based client/server protocol. Its kinda nasty at the moment. Attachments are also in the works [2]. > 3) No user accounts .... [See my response in a new thread] > ~ > Doug. Cheers Joseph [1] http://codereview.waveprotocol.org/106001/show [2] http://codereview.waveprotocol.org/107001/show -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
