![]() 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |