Thanks Andrew, Yes, in light of this project, and other projects that might depend on parts of the wave-protocol code base (whether the model, protocol, or parts of FedOne), we will start releasing versioned packages.
These can be downloaded at http://code.google.com/p/wave-protocol/downloads-- of most interest in this context is fedone-api-0.2.jar, essentially a jar of all the wave-protocol code excluding the executable parts (the server, console client, and echoey agent). The purpose of releasing this is to prevent external code breaking whenever we change the repository. For right now we can't promise the the API will remain backwards compatible, but it will eventually evolve to have that characteristic. We will try and not be needlessly disruptive. Future releases of the API will be announced on this mailing list, with changelogs. Incidentally, we will hopefully release javadocs for the API soon -- Ben On Thu, Aug 27, 2009 at 12:43 AM, Andrew Hyatt <[email protected]> wrote: > > > Offline, I've talked to some of the developers on this repository, and > we decided that it makes most sense for all the new clients, including > the emacs one, to be in separate repositories. I will announce here > when the new emacs-client repository is up. > > Andrew Hyatt <[email protected]> writes: > > > Hi everyone! > > > > A few of us at Google are working towards an Emacs client for Wave in > > our 20% time. We'd like to start contributing to the FedOne client, > > namely: > > > > 1) Creating a new interaction with the FedOne codebase that is a REPL. > > As mentioned in the FAQ, there is no client/server protocol. But, this > > is a place to start, and we think that our REPL client will be a > > client/server protocol. Our interface will be of a general nature > > (specifically, not using S-expressions), perhaps simple commands and > > JSON replies. > > > > 2) We'd also like to have the emacs client code be part of this > > codebase. First of all, anyone using the emacs client has to have > > FedOne's jar anyway, plus the scripts around it. If, at a future time, > > our emacs client is no longer dependent on FedOne, we would move it out > > to a new codebase. > > > > There is some interest in putting Wave on Emacs, as you can see from > > this EmacsWiki page: > > > > http://www.emacswiki.org/emacs/Google_Wave_for_Emacs > > > > I'm attaching a patch with a few README files in a few new directories > > that represents a start to this project (where the commit is basically a > > signal to us that we can proceed on this approach). If and when the > > directory structure gets in the codebase, we'll start putting info up on > > the wiki page mentioned above, and discussion can start among the > > general emacs community. Then we can proceed in building the things > > we've described. > > > > Opinions or other feedback is welcome. Thanks! > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
