To clarify, we do plan on adding real-time collaboration to JupyterLab On Fri, Aug 5, 2016 at 9:09 AM, Matthias Bussonnier <[email protected]> wrote: > Hi Pablo, > > The current state of JupyterLab is to reach feature parity with the > current notebook, then we will look at extending the functionality. > We'll likely start to investigate before, but not at full speed. > > We don't have the ability yet in lab to have the notebook in it's own page. > -- > M > > On Thu, Aug 4, 2016 at 9:29 PM, <[email protected]> wrote: >> Hi Fernando, >> >> What is the scope of JupyterLab? >> https://github.com/jupyter/jupyterlab >> >> The README says: >> "An extensible computational environment for Jupyter" >> >> I'm not sure what it means but it seems to have a broader scope than just >> hooks for OT. >> Will I be able to use OT with a notebook with minimal UI? For example >> without a file browser. >> >> Is there a specific issue can I track for progress? >> >> Thanks >> >> On Thursday, August 4, 2016 at 4:00:15 AM UTC+3, Fernando Perez wrote: >>> >>> Hi Pablo, >>> >>> On Wed, Aug 3, 2016 at 5:46 PM, <[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> Can several users edit the same notebook in real-time or maybe it's on >>>> the roadmap? >>>> >>>> If not, how can we implement it? >>>> What's needed is a way to handle operational transformation ops per cell >>>> on the server and client. >>>> On the server we need a gateway between the client and the kernel that >>>> will transform ops and inform other clients. >>>> On the client we need a way to receive ops, transform them and push >>>> changes to cells. >>>> >>>> Any pointer? >>> >>> >>> Yup, we think that with the APIs in JupyterLab this will be in general >>> much easier to implement, as they have been designed precisely with that in >>> mind. Ian Rose is a new postdoc starting in a few weeks with me at Berkeley >>> who will focus on that problem; now that we're getting JLab in a pretty >>> usable state for everyday work, we hope to move quickly on this... >>> >>> Cheers >>> >>> f >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Project Jupyter" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jupyter/ec7505c3-b7b3-4c13-b6d6-8e183957b3bd%40googlegroups.com. >> >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Project Jupyter" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jupyter/CANJQusXhNO0xgCRzVkHAP3SGmm0B1YZ%2BkoHg0TSNKjA74Zcv2g%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout.
-- Brian E. Granger Associate Professor of Physics and Data Science Cal Poly State University, San Luis Obispo @ellisonbg on Twitter and GitHub [email protected] and [email protected] -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAH4pYpTqYrTp6VpQ5HzU9YJZUARRAVLU_-D61E1xgvaBGzaWow%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
