[Sugar-devel] Collaboration support for sugar web activities
emildudev at gmail.com
Sun Jan 12 13:01:03 EST 2014
About the telepathy part to send only the invites and establish the
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).
Exchanging the TogetherJS ID is not a problem. The invited user can't seem
to connect to the telepathy channel properly.
As you noted above, it's a protocol mess.
If telepathy is completely dropped for web activities, then a question
arises: how to send the invite with the unique ID?
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
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.
On Sun, Jan 12, 2014 at 7:01 PM, Daniel Narvaez <dwnarvaez at gmail.com> wrote:
> 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
>> 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
>> 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.
>> 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
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel