Ah yes, thanks Yuri. It was wave-summit talks. Three I found very important
in the context of code internals:
Day 1: Wave model deep dive
Day 3: Real Time Editor and doodads
Day 2: Wave Panel and Rendering
On Fri, Apr 5, 2013 at 12:36 AM, Yuri Z wrote:
> Here are some links to Wave Summit talk
Here are some links to Wave Summit talks.
https://cwiki.apache.org/confluence/display/WAVE/Wave+Summit+Talks
On Thu, Apr 4, 2013 at 10:03 PM, Pratik Paranjape wrote:
> @Willie I don't think an all pervasive event bus exists in the code, if
> that is what you are looking for. Someone will correc
@Willie I don't think an all pervasive event bus exists in the code, if
that is what you are looking for. Someone will correct me if
following explanation is wrong.
The the keystrokes are first seen by the Editor (see EditorImpl), they are
categorized between commands for annotations
and text inpu
In theory its perfectly possible to build a wave client without using GWT -
you can even have a non-browser based client. Pre-apache there was Android
native prototypes, for example.
However, I believe the interface between the server and client is probably
going to change. At least, last time I i
You can also take a look at the following table, which briefly describes
various Wave packages.
On Thu, Apr 4, 2013 at 9:39 PM, Yuri Z wrote:
> Also take a look into org.waveprotocol.wave.concurrencycontrol
> and org.waveprotocol.wave.client.concurrencycontrol packages
>
>
> On Thu, Apr 4, 2013
Also take a look into org.waveprotocol.wave.concurrencycontrol
and org.waveprotocol.wave.client.concurrencycontrol packages
On Thu, Apr 4, 2013 at 9:36 PM, Yuri Z wrote:
> I think then, you should take a look at
> the org.waveprotocol.box.server.waveserver.WaveBus interface.
>
>
>
> On Thu, Apr
I think then, you should take a look at
the org.waveprotocol.box.server.waveserver.WaveBus interface.
On Thu, Apr 4, 2013 at 9:16 PM, Willie Slepecki wrote:
> If im reading the documents right, the federation system is the transport
> system between two wave servers. in laymans terms, its wav
If im reading the documents right, the federation system is the transport
system between two wave servers. in laymans terms, its waves version of
SMTP, basically where google tried replacing email servers. that part i
have no interest in (at this time), maybe in the future i will want the
ability
If you refer to the Wave Federation Protocol, then yes it is implemented as
part of the server. However, federation wasn't tested for a while...
On Thu, Apr 4, 2013 at 11:16 AM, Willie Slepecki wrote:
> Ok, i see what you are doing now. Well that fits into what i wanted to do
> very well. I d
Ok, i see what you are doing now. Well that fits into what i wanted to do
very well. I don't want my system to be built around wave, i want wave to
be a component of a much larger system. In order to do that I will pull
this apart into more fine grained modules and be able to use those modules
a
Hi
Google did not open the source of original Google Wave, but instead it
created a stand alone open source implementation, with some core parts -
like the OT implementation - being ported as is. But the client was rebuilt
from the scratch.
The current implementation saves all the deltas, so it is
is the history replay in the old code repo and just hasn't been ported yet
or did google not release it.
I have been looking at the code for several hours now. its in pretty rough
shape but good enough to run i guess. I had to fix several issues in the
code to get it to compile but it appears to
Hi
You can find the source code at
http://incubator.apache.org/wave/source-code.html
The current implementation supports concurrent edition of the document by
several users, but there's no implementation for history replay.
You can take a look at demo server: waveinabox.net
Regarding your needs - i
I am looking into building a sort of collaborative document management
application. I remembered wave from the google beta days and I remember it
having two features that just astonished me, two features that could
complete my design for this new CMS system im designing.
the first feature was its
14 matches
Mail list logo