incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pablo Ojanguren <>
Subject Re: Previous attempts at separating the client
Date Sun, 26 Jul 2015 18:58:30 GMT
Hi Evan,

I am responsible of that fork, SwellRT as Thomas has pointed out. It
provides two clients:

JavaScript: it uses the original client's Java/GWT code to manage the wave
protocol stuff. On top of it, a native JavaScript layer is provided. So I
have dropped all original IU related code.

Android: it uses the original Java client's code, replacing native
GWT/JavaScript parts by Java/Android compatible, basically the Websockets

The aim is to allow a general use of the Wave data model
(Participants, Wavelets & Documents) via an API.

Hence, it separates IU code but it still reuse part of the original
client's Java/GWT code. I think to port non-UI client parts to other
language would be a huge effort.

El sábado, 25 de julio de 2015, Thomas Wrobel <>

> I tried to separate them out a few years ago and got nowhere, so I cant
> help personally.
> However, when asking about it a few months back I was pointed to this fork
> of wave;
> That project has a server with a JavaScript API allowing various sorts of
> clients to access it.
> Its possible that it might give some insights into how to separate?
> ~~~
> Thomas & Bertines online review show:
> Try it! You might even feel ambivalent about it :)
> On 25 July 2015 at 17:52, Evan Hughes < <javascript:;>>
> wrote:
> > Hello,
> >
> > Im looking for any developers still here that have attempted to separate
> > the client to share their experiences, as I've been wrapping my head
> around
> > the client to be able to update the gwt and improve performance and bugs.
> >
> > So if you have any experiences or advice in general would you be kind
> > enough to share it here.
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message