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

Support for Plotly #373

Closed
tuscland opened this issue Sep 23, 2024 · 6 comments · Fixed by #381
Closed

Support for Plotly #373

tuscland opened this issue Sep 23, 2024 · 6 comments · Fixed by #381
Assignees
Labels
enhancement New feature or request

Comments

@tuscland
Copy link
Member

Plotly is a popular scientific charting library. It has a JSON schema similar to Vega in order to author and share charts. I suggest we support it. @MarieS-WiMLDS, WDYT?

See https://plotly.com/chart-studio-help/json-chart-schema/

@MarieS-WiMLDS
Copy link
Contributor

100% agree, it's more and more used.

@tuscland tuscland added the enhancement New feature or request label Sep 23, 2024
@sylvaincom
Copy link
Contributor

Yes plotly is super powerful, I use it a lot (more than Altair) ; even people in academia use it

@thomass-dev
Copy link
Collaborator

thomass-dev commented Sep 23, 2024

@rouk1 how do you estimate the complexity of integrating a plotly-json in the frontend ?
In the backend, its simple as altair... i've drafted a PR.

@thomass-dev thomass-dev linked a pull request Sep 23, 2024 that will close this issue
2 tasks
@rouk1
Copy link
Contributor

rouk1 commented Sep 24, 2024

I suppose that if we store a json that match plotly's schema we will be ok on the frontend.

@thomass-dev
Copy link
Collaborator

thomass-dev commented Sep 24, 2024

I let you work directly on #381? Or you prefer to work on a separate PR?

@rouk1
Copy link
Contributor

rouk1 commented Sep 24, 2024

Let's do it in 1 PR : )

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

Successfully merging a pull request may close this issue.

5 participants