Status of project
Andrew Hyatt
This is the first message to the discussion mailing list. I thought
I'd give a quick overview of what is going on, although the code
itself also has an explanation.
I'm working on this project as my 20% project (I currently work for
Google). A few colleagues and myself have started this project to
enable emacs to be a client to Google Wave. Our plan:
1) Integrate with the FedOne server that is part of the
wave-federation open source project
(http://code.google.com/p/wave-protocol/)
2) Construct a simple least-effort REPL client that uses the FedOne
client. The beginnings of this already exist in the code.
3) Create the emacs code that connects to the REPL and can get
information in a standard format.
4) Create the emacs UI, starting with just the list of waves, then
creating the UI to view waves, then to create, then to edit.
A few external events will influence the project. First, the FedOne
server will be able to communicate with real Wave servers once Google
implements the federation protocol. Secondly, a real client/server
protocol will emerge. Since emacs may be the first real client, we
hope we can constructively influence that project. When it is real,
we will replace our interaction with the FedOne client with that
client/server protocol. Eventually, Google may implement that
client/server protocol, and we can directly integrate against a
particular Wave server then.
If anyone is willing to lend a hand, and can pledge some support, I
have a small amount of Wave invites to give away :)
I hope this explanation helps. Please send any questions or concerns.
I'm looking forward to getting this working!
Mulander
2009/10/4 Andrew Hyatt <ahy...@gmail.com>:
>
> If anyone is willing to lend a hand, and can pledge some support, I
> have a small amount of Wave invites to give away :)
>
I'm more than willing to help both with implementation and testing.
I have some elisp development under my belt, this isn't much but I'm all
for improving and a wave client for Emacs is a great motivation to
gain momentum.
I have a full time job, but I could work on the projects on weekends
and probably
on most days after work.
If You consider me a valuable asset to the project then pass a
invite to netprobe { at } gmail [dot] com
One idea for the future, it would be nice to create an org-mode bot
for google wave,
so we could produce org waves from Emacs and people using the regular
client could
interact with them in a similar way that we all do. What do You think?
Andrew Hyatt
project right now; you can certainly start to contribute without being
on Wave. I'm planning on submitting the beginnings of an emacs client
in the next week. I'm hoping that after that you should be able to
contribute fairly easily.
Mulander
>
> Invited. Note that this invitation has really no effect on the
> project right now; you can certainly start to contribute without being
> on Wave.
to netp...@gmail.com
or could gmail classify it as spam? It's good to know that significant
work can be done without
access to a wave account I'll try working on it as soon as You release
the stub for the client.
> I'm planning on submitting the beginnings of an emacs client
> in the next week. I'm hoping that after that you should be able to
> contribute fairly easily.
I understand correctly the code will appear there?
Andrew Hyatt
The wave invites aren't immediate. One person I invited got theirs the next day, another still hasn't received it. I would guess you should get it in a week's time at most.
And yes, the emacs code will be part of this project's code.
Thanks for volunteering!
On Oct 4, 2009 11:38 AM, "Mulander" <netp...@gmail.com> wrote:2009/10/4 Andrew Hyatt <ahy...@gmail.com>: >
> Invited. Note that this invitation has really no effect on the > project right now; you can certa...
I didn't receive the invitation can You check if it was sent correctly
to netp...@gmail.com
or could gmail classify it as spam? It's good to know that significant
work can be done without
access to a wave account I'll try working on it as soon as You release
the stub for the client.
> I'm planning on submitting the beginnings of an emacs client > in the next week. I'm hoping th...
Brad Collins
> If anyone is willing to lend a hand, and can pledge some
> support, I have a small amount of Wave invites to give
> away :)
>
I am happy to do what I can to help. I've contributed to a
couple of emacs projects in the past.
I'm a bit rusty at the moment, mostly because most of my
time is spent on the road pitching to investors to keep our
startup afloat...
I already have accounts in the Wave Sandbox and Preview. My
user name is 'deerpig'.
I look forward to seeing the code!
b/
--
Brad Collins <br...@chenla.la>
skype|twitter|wave: deerpig
Joseph Gay
This is quite an exciting project! I would most certainly like to lend
a hand. I have a little lisp/elisp experience, a fair amount of java,
and of course I use emacs on a day-to-day basis. My user name on the
wave dev sandbox is joseph.gay, and I also have an account on the wave
preview under gilleylen.
I am able to work on Sunday evenings and an additional 5 or so hours
per week. I'll get started with some reading and try to get up to
speed. Thanks Andrew for this initiative!
Daniel Renfer
participate. I have about a year's worth of Clojure experience and am
fair at elisp programming.
I never got a sandbox id, but I'm duck112358 on Google Wave.
Andrew Hyatt
If you are interested in working on the server side with the clojure
code, you can get started now. Here's the things I was thinking we
could use:
1) An interface for retrieving a particular wave. The client can call
a method to open a particular wave by id, and get all the relevant
info from the wave, suitable for emacs to put into a buffer.
2) Methods to create a wave.
3) A way to watch a wave. Probably this will be a different port,
which means modifying the startup script. But then the clojure code
will just listen for notifications and output updates that would be
useful for emacs to update its buffers.
This is all a bit hand-wavy at the moment, but hopefully you can help
solidify it. Thanks for the offer of help!