Of what benefit would contributing this to wave be?

Doesn't wave do a superset of this functionality already? (albeit with
messier code)
Seems (possibly) more useful for Wave to contribute its (federation)
functionality to this or a fork of it. Then you would have a new
pseudo-wave that does much of the same stuff, but with a much neater
codebase (and mobile support) to build from.
Alternatively if elements of this could replace waves code to
simplify/neaten it that might be good...but at least from an outsiders
perspective that seems rather hard.

Regarding the point earlier about rich text in json - wouldn't it be easier
to use html encoding of styled text? To my knowledge html strings work in
json just fine as long as a few things are escaped. Or isnt this possible
with the OT method being used?





~~~
Thomas & Bertines online review show:
http://randomreviewshow.com/index.html
Try it! You might even feel ambivalent about it :)


On 9 July 2014 17:06, 田传武 <i...@goodow.com> wrote:

> inline
>
> On Wed, Jul 9, 2014 at 4:43 PM, Christian Grobmeier <grobme...@gmail.com>
> wrote:
>
> > What are your plans with it?
> >
>
> Not sure, may depend on the feedback.
>
>
> >  Are you considering to contribute this to Wave?
> >
>
> I've read most of wave's code, but when I try to do big refactor, I am
> baffled.
>

Reply via email to