At this moment I don't see Wave as a downstream dependency of SwellRT.
(SwellRT depending on Wave, right?)
SwellRT has modified Wave in different parts, so there is not a clear
separation of responsibilities right now.
Personally I would rather Wave to take over SwellRT entirely and liberate
Wave
Pablo,
+1 on this approach. I think this is the best idea if we can pull it off.
~Michael
On 3/21/17, 8:30 AM, "Pablo Ojanguren" wrote:
At this moment I don't see Wave as a downstream dependency of SwellRT.
(SwellRT depending on Wave, right?)
SwellRT has modified Wave in different
+1; I think a lot of us have voiced support over the years for decoupling
the Wave server from its current GUI, and it sounds like this approach
would be a great shift in that direction.
Zachary Yaro
On Tuesday, 21 March 2017, Michael MacFadden
wrote:
> Pablo,
>
> +1 on this approach. I think t
yep, I agree even if this is painful.
+1
On Tue, Mar 21, 2017 at 8:56 PM Zachary Yaro wrote:
> +1; I think a lot of us have voiced support over the years for decoupling
> the Wave server from its current GUI, and it sounds like this approach
> would be a great shift in that direction.
>
> Zachar
Swellrt still relies on the gui side though, the OT transform layer made in
the server is exported through the gwt. So it's not just dumping the client
side code and making a rest API. A significant portion of code will have to
be written in a client side language like typescript or optionally we
e
