search

opencaesar / oml-vision

A VS Code extension providing UI viewpoints for OML models
Other
4 stars 2 forks source link

Integration of Quarto / Jupyter Notebook Extensions with OML-Vision #82

Open UTNAK opened 6 months ago

UTNAK commented 6 months ago

Checklist before submitting a feature request

Is your feature request related to a problem? If yes, describe the problem

I want to execute cells in Quarto or Jupyter Notebook using OML-Visio UI/UX like the vision run gradle tasks.

Describe the desired feature

One of the cool features of OML-Vision is standing on the open-source VSCODE eco-system. I want to use the capability of OML-Vision to integrate other extensions, especially the markdown notebooks with executable code such as Quarto or Jupyter.

quarto-vscode Jupyter Extension for Visual Studio Code

When we have a GUI of these notebooks within the oml-vision, users who are not familiar with coding can access the analysis capability using oml-vision.

Here is a image of integration but not limited in this layout.

image

pogi7 commented 2 months ago

@UTNAK I made preliminary sketches in Figma on what this integration with the Quarto / Jupyter Notebook extensions would look like. If these sketches meet your requirements I will move onto the design.

Initial Setup (Entry Point of Feature): image

Quarto / Jupyter Notebook Installed (the picture only shows quarto but it would look similar for Jupyter notebook) Also the Navigate Webview Pages view will still be there in the final product image

UTNAK commented 2 months ago

Cool! I like the UI/UX of this feature!

pogi7 commented 2 months ago

@UTNAK It looks like integration with the Quarto VSCode extension is impossible until an API is added to the extension. Please refer to the issue for more details. https://github.com/quarto-dev/quarto/issues/547

Integration with the Jupyter VSCode extension can continue as normal since there is an API.

pogi7 commented 2 months ago

@UTNAK After researching the Jupyter VSCode extension there's no way to run cells in the same way that Gradle's VSCode extension does so the scope of the this ticket should be changed to reflect the current limitations of the Jupyter and Quarto VSCode extensions.