<div dir="ltr"><div><div><div>About the telepathy part to send only the invites and establish the connection:<br></div>I can't seem to be able to complete the invitation accepted process. Sometimes it works, sometimes not (mostly not). For normal sugar activities it's the same (with the exception that with them it mostly works, at least I think it works).<br>
</div><div>Exchanging the TogetherJS ID is not a problem. The invited user can't seem to connect to the telepathy channel properly.<br></div>As you noted above, it's a protocol mess.<br></div><div>If telepathy is completely dropped for web activities, then a question arises: how to send the invite with the unique ID?<br>
<br></div><div>Also, I still don't like using 1 server and having everything else depend on that 1 server. The server would most likely have to process a lot of traffic.<br>Would it be possible to use a peer to peer connection with web sockets? Browsers don't support this, with reason. But if sugar's core is used, it should be possible.<br>
<br></div><div>Emil Dudev<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jan 12, 2014 at 7:01 PM, Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">It might not come that easily but I think we need to support non-degraded collaboration between web activities inside Sugar. We don't need to interact with telepathy to do that, just with the UI layer. Telepathy and a new API can co-exist pretty easily.<br>
</div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On 12 January 2014 11:20, Lionel Laské <span dir="ltr"><<a href="mailto:lionel@olpc-france.org" target="_blank">lionel@olpc-france.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br></div><div class="gmail_extra">Collaboration means exchanging data between activities. It's the easy part because we could found lot of technologies that could do that: webRTC, web sockets or any higher layer API on top of it (like the nice TogetherJS API).</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">BTW today collaboration in Sugar means also:</div><div class="gmail_extra">- include a button "share" in the toolbar of the activity,</div><div class="gmail_extra">
- see shared activities in the network view near the buddy icons,</div><div class="gmail_extra">- join a shared activities in the network view so Sugar could launch it in the shared context,</div><div class="gmail_extra">
- send invitation that Sugar will put in the border of the invited users.</div><div class="gmail_extra"><br></div><div class="gmail_extra">None of this features will come easily if we don't reuse Telepathy in Sugar web collaboration because all of these features are handled by Sugar core.</div>
<div class="gmail_extra">It's what I called "degraded collaboration experience": Sugar web activities will have to implement invitation outside Sugar core.</div><div class="gmail_extra"><br></div><div class="gmail_extra">
Because, by definition, Sugarizer can't use Telepathy, it's a place where I hope to reproduce the full experience on top of the collaboration API we'll decide to choose.</div><div class="gmail_extra"><br></div>
<div class="gmail_extra"> Lionel.</div><div class="gmail_extra"><br><div class="gmail_quote">2014/1/11 Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>On 11 January 2014 12:19, Lionel Laské <span dir="ltr"><<a href="mailto:lionel@olpc-france.org" target="_blank">lionel@olpc-france.org</a>></span> wrote:</div>
</div><div><div class="gmail_extra"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">
<div><br></div><div>1) Sugar Web collaboration should be different than Sugar Collaboration. I think that trying to join both will expand complexity. Plus I don't see any use case where a Sugar Web Activity need to communicate with a Sugar Python Activity.</div>
<div><br></div><div>2) Of course if Sugar Web collaboration is different from Sugar Python Collaboration, it ask the question how to handle network view, activity invitation, join an activity, ... So invitation has probably to be handle into each web activity and we'll have a degraded collaboration experience - except in Sugarizer (see below).</div>
</div></blockquote><div><br></div></div><div>Not quite understanding this. Are you saying that when running inside Sugar web activities will provide a degraded collaboration experience? Why?<br></div></div></div></div></div>
</blockquote></div><br></div></div>
</blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Daniel Narvaez<br>
</font></span></div>
<br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br></div>