Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notebook support for Qute #420

Open
angelozerr opened this issue Nov 26, 2021 · 4 comments · May be fixed by #546
Open

Notebook support for Qute #420

angelozerr opened this issue Nov 26, 2021 · 4 comments · May be fixed by #546
Labels

Comments

@angelozerr
Copy link
Contributor

angelozerr commented Nov 26, 2021

I already implemented that in my POC, here a demo.

QuteNotebookDemo

It should be nice to integrate it and improve it in vscode-quarkus.

@angelozerr
Copy link
Contributor Author

@mkouba @maxandersen what do you think about providing notebook support for Qute (see the demo).

I had implemented this notebook support in my POC but it is not integrated in vscode-quarkus. It's just a POC and it could be improved by replacing JSON cell with Java cell for instance.

Thanks for your feedback.

@mkouba
Copy link
Collaborator

mkouba commented Jan 21, 2022

I've never used "notebooks" in IDE. Is it some kind of prototyping tool?

@maxandersen
Copy link
Collaborator

i like the idea, but how would it work ? do i create a pair of files and then run/combine them or how ?

@angelozerr
Copy link
Contributor Author

My POC uses basic feature of notebook, it means that the JSON cell and the Qute cell content are stored in one file (serialized as JSON). But I agree with you,it should be better to stores the JSON cell content in the notebook and the Qute template in the external file (in the real Qute template file).

I don't know if it's possible.

@JessicaJHee JessicaJHee linked a pull request Sep 14, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants