Julia lighttable6/2/2023 I agree with that it’d be good to have this meeting in a place that the JupyterLab/Notebook communities can interact, ask questions, etc. Thanks for reaching out! I’m excited to hear about how the Julia community has been navigating these issues, and where they see this space moving forward. Video 1 is (there is a very short demo of the notebook PR in there) and video 2 is. My email is and we just had two talks at Juliacon about the state of the Julia VS Code integration, that might be a quick way to get a sense of the functionality we have. Could one of you take the lead in setting up such a meeting? I really only know and from this thread, so wouldn’t really know who should be invited. In particular I’m just very, very familiar with the VS Code extension points, which might be useful for that discussion. I could probably say a few things about that as well. I also saw that there were various discussions ongoing about Theia, and how Jupyter might in general be able to integrate more with that or VS Code directly. I could report a bit on what our plans are on the Julia extension side of things. In any case, I think some generic meeting would be great. is entirely distinct and unrelated from the existing Jupyter notebook support in the Python extension for VS Code). I’m a huge JupyterLab fan, but when I recently realized that we will probably have the premier notebook UI for Julia in VS Code and not JupyterLab, it did give me pause and made me wonder about the larger strategic implications for JuptyerLab… I say “recently realized” because there was very little strategy behind any of this on our end, it was more that all of this fell into place when MS started to work on the notebook API (which btw. support from day one because we built these things pre-notebook days and they can now be integrated with almost no extra work into the notebook UI. ![]() We’ll have full language server, debugger, workspace viewer, plot pane, documentation browser etc. Certainly a possibility, but a the moment we are much more focused on getting the actual functionality of the notebook UI up and running, rather than focus on the the file load and save story.īut one thing is becoming pretty clear in this process: the notebook UI we will end up with is going to be much richer than what Julia users will have in JupyterLab. We have a PR that implements a native notebook editing and run experience for Julia in VS Code and it uses a custom file format, but the whole thing is WIP at the moment and whether we will go with a custom format or not is up in the air right now. I should clarify probably one thing right away: we have not made a decision to create our own notebook format. Hi everyone! excellent session at Juliacon last week made me think that it would be good to have some more contact between the Julia VS Code team and the Jupyter effort, so I browsed around and the first thing I see is this thread So here I am, and I think it is a great idea to connect!
0 Comments
Leave a Reply. |