-
-
Notifications
You must be signed in to change notification settings - Fork 292
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
DataFrames.jl+Pluto.jl integration #2206
Comments
I think it would be really cool to have an interactive table display in Pluto for DataFrames as default, with searching, filtering, sorting and pagination. Some time ago I did some experiments with agGrid (https://github.com/lungben/PlutoGrid.jl ), what looks quite promising. |
VSCode had the same issue (also TerminalPager.jl) - the only solution is paging loading of data frame data into cache AFAICT. |
x-ref JuliaData/DataFrames.jl#3096 (comment) (just to keep track all comments in one place) |
It looks like the PR is fine from Pluto's perspective because, like Ronan mentioned, Pluto does not call the default HTML show method unless you explicitly ask it to (using something like AsMIME.jl). About the CSS styles: all our custom styling is scoped to our custom viewers only, so it will not interfere with PrettyTables.jl. We designed a custom table viewer because we wanted to improve the default in DataFrames.jl, and because we want to support lazy loading more rows and columns. Lazy loading is still very important, so we will keep our custom viewer for now, but I would be interested to look at the improvements in PrettyTables.jl and bring some of them to Pluto! |
I understand that it is frustrating right now that all the cool work into PrettyTables.jl and DataFrames.jl will not be visible to Pluto users, but let's try to get some of the nice new features into Pluto soon! |
It is fine from DataFrames.jl perspective. |
In JuliaData/DataFrames.jl#3096 (comment) there is a question on DataFrames.jl+Pluto.jl integration.
The issue is:
The question is should we go forward with it (i.e. let Pluto.jl override the settings of DataFrames.jl or this should be somehow synchronized).
On DataFrames.jl side the issue is triggered by the fact that we want to switch to PrettyTables.jl for HTML rendering.
The text was updated successfully, but these errors were encountered: