Collaborative simultaneous editing

[dtkaplan]

It would be nice in a classroom setting to be able to edit the contents of an exercise chunk in collaboration with other people. The isolation of chunks from each other would prevent this from becoming too complex for the users. Maybe this could be setup via the URL query string, e.g.

https://dtkaplan.shinyapps.io/Workshop_wrangling?share=d4a78

The instructor, or whoever, could post the URL on, say, the course syllabus for that day. I'm imagining that this behavior would be tied to the use of a particular server, e.g. shinyapps.io or rcloud.

[jjallaire]

This is technically possible via Ace integration with Firepad (https://firepad.io/docs/#getting_started_with_ace). @kevinushey and @jmcphers Would this be pretty straightforward assuming public Firebase is used as the backing store?

[jmcphers]

It's straightforward, but session management is going to be finicky. Firepad (at least when we integrated it with RSP) has to start with an empty editor surface. So some process needs to be in charge of (a) creating the appropriate Firebase instance for each chunk, and (b) populating it with its initial contents (in RSP we do this by synthesizing a text insertion atom that includes the entire doc). This is better done explicitly somewhere for security/cost reasons but could all be done implicitly depending on your appetite for risk. :-)

Once you've got a warm Firebase instance it's all downhill (just a matter of a little JS glue to start with empty editors and inject the Firepads in).

[jjallaire]

Okay, thanks. Not a slam dunk but it sounds like we could get it work if we put some effort in.

…

On Thu, May 18, 2017 at 1:20 PM, Jonathan ***@***.***> wrote: It's straightforward, but session management is going to be finicky. Firepad (at least when we integrated it with RSP) has to start with an empty editor surface. So some process needs to be in charge of (a) creating the appropriate Firebase instance for each chunk, and (b) populating it with its initial contents (in RSP we do this by synthesizing a text insertion atom that includes the entire doc). This is better done explicitly somewhere for security/cost reasons but could all be done implicitly depending on your appetite for risk. :-) Once you've got a warm Firebase instance it's all downhill (just a matter of a little JS glue to start with empty editors and inject the Firepads in). — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#74 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGXx2M4Mkp4fbkgcyhIRdMNwBqD4uxdks5r7H3XgaJpZM4NfJUz> .