Re: [Sugar-devel] Regarding JS collaboration project

2014-03-09 Thread Daniel Narvaez
If I remember correctly Emil also agreed that the new framework should be
independent from telepathy at some point and even worked on it.


On 9 March 2014 06:45, Prasoon Shukla prasoon92.i...@gmail.com wrote:

 Hi Sam. Sorry for the late response but I was occupied with academics.

 Anyway, I need to bother you again with some questions.

 So, I went through the thread by Emil Dudev and read the arguments he made
 in favour of not using the mozilla node server and using telepathy instead.
 To that, dnarvaez said that using the node server might be a better idea
 since the current protocol is very unstable.

 Now, I am somewhat familiar with sugar codebase but certainly not enough
 to actually discuss the merits or demerits of either of these approaches
 (although personally, I like better the idea of all communication happening
 over websocket via a node server). So, the final decision on which approach
 to take will be in the hands of those more experienced. But as I said
 before, I would prefer it if we use the websocket protocol to have this
 kind of architecture:

 |Sugar Web Activity| - |Sugar Shell|
\
 \
  websocket
   \
 |Node Server|
/
   /
  /
 |Sugar Web Activity| - |Sugar Shell|

 instead of the usual telepathy based communication. This I would like
 because:
 1. We'll be able to use the mozilla server with modifications as needed.
 2. We'll be able to use the *huge* node.js ecosystem for realtime
 communication in any way we want! And, websocket is very versatile -  we
 can send pretty much any binary data over the network.

 Also, I've worked with node before and found the communication to be quite
 reliable (which it is not with the current XMPP based protocol, if I
 understood dnarvaez correctly). That said, I've only tested out my node
 based work with a handful of people, so...

 The only downside is the need to have a node server running. For the case
 when there is not internet connectivity, I think we can make a set of
 scripts that can be called to run a node server on the one of the machines,
 say that of the teacher, and all others will connect to it. And of course,
 this process needs to be simple.

 Anyway, it just seems right to me to augment JS activities with a JS based
 collaboration framework. But of course, I don't really know the details all
 too well to be making the decision here.

 So, can you please comment on this? Once this decision is made, I can
 start working on my application.

 Thanks
 ᐧ

 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Regarding JS collaboration project

2014-03-09 Thread Prasoon Shukla
 If I remember correctly Emil also agreed that the new framework should be
independent from telepathy

It seems there were two separate threads of the same name:

1 - http://lists.sugarlabs.org/archive/sugar-devel/2014-January/046687.html
2 - http://lists.sugarlabs.org/archive/sugar-devel/2014-January/046773.html

and I just read the first one _

Anyway, it's good to see that we don't want to use telepathy for this. So,
I'll go ahead and take a look at Emil's code and run it. Will reply back at
this thread soon.


On Sun, Mar 9, 2014 at 4:42 PM, Daniel Narvaez dwnarv...@gmail.com wrote:

 If I remember correctly Emil also agreed that the new framework should be
 independent from telepathy at some point and even worked on it.


 On 9 March 2014 06:45, Prasoon Shukla prasoon92.i...@gmail.com wrote:

 Hi Sam. Sorry for the late response but I was occupied with academics.

 Anyway, I need to bother you again with some questions.

 So, I went through the thread by Emil Dudev and read the arguments he
 made in favour of not using the mozilla node server and using telepathy
 instead. To that, dnarvaez said that using the node server might be a
 better idea since the current protocol is very unstable.

 Now, I am somewhat familiar with sugar codebase but certainly not enough
 to actually discuss the merits or demerits of either of these approaches
 (although personally, I like better the idea of all communication happening
 over websocket via a node server). So, the final decision on which approach
 to take will be in the hands of those more experienced. But as I said
 before, I would prefer it if we use the websocket protocol to have this
 kind of architecture:

 |Sugar Web Activity| - |Sugar Shell|
\
 \
  websocket
   \
 |Node Server|
/
   /
  /
 |Sugar Web Activity| - |Sugar Shell|

 instead of the usual telepathy based communication. This I would like
 because:
 1. We'll be able to use the mozilla server with modifications as needed.
 2. We'll be able to use the *huge* node.js ecosystem for realtime
 communication in any way we want! And, websocket is very versatile -  we
 can send pretty much any binary data over the network.

 Also, I've worked with node before and found the communication to be
 quite reliable (which it is not with the current XMPP based protocol, if I
 understood dnarvaez correctly). That said, I've only tested out my node
 based work with a handful of people, so...

 The only downside is the need to have a node server running. For the case
 when there is not internet connectivity, I think we can make a set of
 scripts that can be called to run a node server on the one of the machines,
 say that of the teacher, and all others will connect to it. And of course,
 this process needs to be simple.

 Anyway, it just seems right to me to augment JS activities with a JS
 based collaboration framework. But of course, I don't really know the
 details all too well to be making the decision here.

 So, can you please comment on this? Once this decision is made, I can
 start working on my application.

 Thanks
 ᐧ

 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




 --
 Daniel Narvaez

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] Regarding JS collaboration project

2014-03-06 Thread Prasoon Shukla
Hi all

My name is Prasoon Shukla. I'll be applying as a student to GSoC 2014.

I have been exploring the possible project candidates (
http://wiki.sugarlabs.org/go/Summer_of_Code/2014) and  JavaScript
collaboration and social help seem like good projects (considering my
competance and previous experience).

Anyway, I haven't been able to decide which of the two projects I really
want to dedicate my attention to. I've already had a chat with Walter about
social help. Now, I'd like to ask a few thing about JS collaboration. (I
couldn't find manuq on IRC, so I'm asking here.)

So, first thing is that I don't quite understand *how* the collaboration is
supposed to work. But perhaps this hasn't been decided by the dev team
either as of yet since the project page says - The first step is to agree
upon a collaboration strategy with the developer team. So, I'd like to
have a discussion on it - Are we going to have a realtime collaboration
model like say, http://conceptboard.com ? Or, do we have a sharing based
collaboration setup which is similar to traditional email/github like
sharing (this will be quite cumbersome, I think)? Also, since the sugar-web
activities will be based on web-technologies, I was wondering if we can
experiment with a server written in node.js (I've found it a great tool for
realtime apps).

The other thing that I'm confused about is the expected result - Rich,
intuitive collaboration *between JavaScript Activities*. How does
collaboration b/w different sugar activities work (Maybe an example)? Or
does this mean the same thing as collaboration b/w different users using
the same activity (which I think should be the case)? This seemed a bit
confusing, so I'd like to get it clarified.

Thanks
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Regarding JS collaboration project

2014-03-06 Thread Prasoon Shukla
Thanks a lot Sam.

 Collab in sugar runs between same activity on different devices.

That's what I was thought :)

Anyway, I took a look at together.js and wow, it's a really awesome
library. So, the thing I talked about writing a node based server - well,
they've already done it for their hub! Hmm... This looks promising.

 I can forward the (massive) thread if you don't have it.

Well, just mailing me the links to the archive on
http://lists.sugarlabs.org/archive/sugar-devel/ would be great. Or, just
let me know the time the discussion began and the title of the thread and
I'll find it in the archives :)

Thanks again.

Prasoon
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Regarding JS collaboration project

2014-03-06 Thread Sam Parkinson
Hi,

The thread is 1/2 way down here:
http://lists.sugarlabs.org/archive/sugar-devel/2014-January/thread.html

It is called [Sugar-devel] Collaboration support for sugar web activities

Sam
On Mar 7, 2014 7:21 AM, Prasoon Shukla prasoon92.i...@gmail.com wrote:

 Thanks a lot Sam.

  Collab in sugar runs between same activity on different devices.

 That's what I was thought :)

 Anyway, I took a look at together.js and wow, it's a really awesome
 library. So, the thing I talked about writing a node based server - well,
 they've already done it for their hub! Hmm... This looks promising.

  I can forward the (massive) thread if you don't have it.

 Well, just mailing me the links to the archive on
 http://lists.sugarlabs.org/archive/sugar-devel/ would be great. Or, just
 let me know the time the discussion began and the title of the thread and
 I'll find it in the archives :)

 Thanks again.

 Prasoon

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel