etherpad compatibility
Joe Corneli
We're setting up a meeting to talk about the future of
Etherpad,
http://etherpad.com/OcfYWSqwqq
and I think it would be just fantastic if we could design
Etherpad to be Emacs-compatible, and so, presumably,
Wave/Emacs compatible. If that makes sense. If you have
any thoughts on this matter please share them!
Thanks,
Joe
PS. If someone at Google is reading this, could you please
mention to the appropriate party that we're wondering
about the /trademark/ status of 'EtherPad'.
Andrew Hyatt
I'm going to ask around about the trademark status of EtherPad. Stay tuned.
About the making EtherPad compatible with this project, there are two
ways you can go about it:
1) Make EtherPad run on top of Wave. The technologies are similar.
You could keep the EtherPad UI and make it run on top of Wave. Of
course, I've only used EtherPad a few times, so there may be features
that are impossible to make work with a Wave backend.
2) Make another backend for our UI. The lisp code here is split into
a wave-client.el, which talks to the wave server, and wave-list.el and
wave-display.el, which handle UI. You can make another backend which
is compatible with wave-list and wave-display. This may necessitate
changes to the data structures we send to represent the data:
http://code.google.com/p/wave-client-for-emacs/wiki/WaveClientDataSpec.
Right now we haven't started implementing the OT parts of the code,
so I can't speculate about how possible it is to share the OT logic
between these different backends yet.
I think it is really nice to try and integrate support EtherPad, and
integrate emacs into it. I hope we can make this project work for you.
Joe Corneli
At first glance it seems like option 2 will work best.
I'm excited to work on getting this going!
> 2) Make another backend for our UI.
Joe
Joe Corneli
Andrew Hyatt
you are wanting to create with etherpad on emacs.