-
Notifications
You must be signed in to change notification settings - Fork 326
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
Chart component #75
Comments
This would be a great feature. These libs are very feature complete: |
I think the simple solution is to return a vega JSON object perhaps from altair and render that in the frontend. I think long term this is an idea that I'm really interested in, and I'd like to try to do something more powerful, particularly WRT interaction etc. |
Also worth considering may be echarts, which has a json format and an (auto-gen) pydantic model in ezcharts. From my limited perspective, there are 2 possible advantages:
|
ye, I agree echarts is probably the best way to go. |
I've been using quarto recently which is great - they recently added a feature to support observablejs code blocks. |
Hi guys, aftering reading the above comments, I still have no idea how to add a chart in the fastui. Can someone show me a piece of codes? |
I made an initial proposal for this here: #201 using |
@tim-habitat Just noticed your PR is kind of stale, has there been any changes? This feature would be huge for |
No nothing changed my side and would be happy to freshen up, though i suspect the team at pydantic might want to implement it in a different way based on the comments above. |
Hi,
I think it would be great if we had a chart component (e.g. think 2D bar charts or scatter plots).
Guess the mechanism of supplying data in the backend could be similar as it is implemented for the
Table
component.For frontend implementation I think we could leverage something like Chart.js to do the charting work itself for us.
Not sure if this use case is common enough such that it would fit into FastUI itself or whether this should rather be considered a custom component and be separate from the package.
Any thoughts?
The text was updated successfully, but these errors were encountered: