-
Notifications
You must be signed in to change notification settings - Fork 12
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
Custom Element for rendering Vega specification #59
Comments
Hi Adrian! 👋 What do you mean by custom element here? Is it a Web Component or something else? |
Exactly, part of WebComponents spec. I was thinking something along the lines of |
I see. This is what Luke Westby was promoting at the recent Elm Europe in his talk – I really like the idea! There already exists a I exchanged a couple of emails with @eterna2 (the author of Feel free to chip in and explore what changes are necessary in |
Sorry for the long wait. Was busy with another project. I have migrated to v3, but it is based on lit-element rather than polymer-element. I have not migrated all the features, but the basic stuff is there. Because we have migrated to npm, the webcomponent link is different now - repo is still the same. https://www.webcomponents.org/element/@polymer-vis/vega-elements U can see a example here: https://bl.ocks.org/eterna2/905451d8c68995e7a2a16254d510e735 Or here: Basically, I have pre-build a distribution which u can use straight off. But u will need to import the lib for Vega and vega-lite yourselves. |
Hi,
What do you think about implementing custom element which could render visualisation from Vega specification? I imagine, we could then simply keep specification in model and pass in view function to custom element. Almost no configuration in JavaScript.
Of course current mechanism should stay in place for more complicated cases, where you want to use
Vega.View
in your code and for example manipulate signals or selections.I understand it would be implemented in another, not elm package. But I would like to discuss such idea here, between elm-vega users.
Best,
Adrian
The text was updated successfully, but these errors were encountered: