[Sugar-devel] Collaboration support for sugar web activities

Daniel Narvaez dwnarvaez at gmail.com
Sun Jan 12 12:01:49 EST 2014

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.

On 12 January 2014 11:20, Lionel Laské <lionel at olpc-france.org> wrote:

> 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).
> BTW today collaboration in Sugar means also:
> - include a button "share" in the toolbar of the activity,
> - see shared activities in the network view near the buddy icons,
> - join a shared activities in the network view so Sugar could launch it in
> the shared context,
> - send invitation that Sugar will put in the border of the invited users.
> 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.
> It's what I called "degraded collaboration experience": Sugar web
> activities will have to implement invitation outside Sugar core.
> 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.
>             Lionel.
> 2014/1/11 Daniel Narvaez <dwnarvaez at gmail.com>
>> On 11 January 2014 12:19, Lionel Laské <lionel at olpc-france.org> wrote:
>>> 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.
>>> 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).
>> Not quite understanding this. Are you saying that when running inside
>> Sugar web activities will provide a degraded collaboration experience? Why?

Daniel Narvaez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140112/fc75fa23/attachment.html>

More information about the Sugar-devel mailing list