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

Visualizations as preview windows #1

Open
deboer-tim opened this issue May 9, 2019 · 3 comments
Open

Visualizations as preview windows #1

deboer-tim opened this issue May 9, 2019 · 3 comments

Comments

@deboer-tim
Copy link

Kui has a number of visualizations for files that will also be in git and hence be in a VS Code user's workspace. Just like in the Markdown link below, it would be extremely cool if we could provide an action on the file types that we recognize and open a visualization window instead of or beside the source editor: https://code.visualstudio.com/docs/languages/markdown

Yes, I realize that this is skipping the command line (which is normally the root and launch point of Kui), but if we have the viz available then this would be a great way to reuse it and expand Kui's base while providing something very useful.

Hmm, you could do a similar thing outside of VS Code by opening just the vis if you type a filename or adding a simple command like "viz pipeline.yaml" or "kui pipeline.yaml".

@myan9
Copy link

myan9 commented May 9, 2019

Nice idea! Kui currently supports a synchronous edit and preview feature for apache-composer. We should start to generalize this feature for a broad/advanced usage. We currently have some distinction between open and edit command, e.g. open a Markdown file shows the rendered version, and edit show the source code. I think introducing a visualization command should be very useful!

@starpit
Copy link
Contributor

starpit commented May 10, 2019

i agree, this is great. we can leverage the vscode "command line" to good effect.

@starpit
Copy link
Contributor

starpit commented May 10, 2019

@myan9 given kui's "prescan" model, i.e. a model of all registered kui commands, we should be able to generate a vscode command registration list automatically, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants