You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optionally export data into a folder so the Parquet data can stay in binary form. Note that the output directory then needs to be served, it can't be opened as a file.
The text was updated successfully, but these errors were encountered:
Right now, we always export all the code and all the data into a single massive HTML file, where the binary buffers are Base64-encoded and saved as big strings. This is a pretty good compromise because it's very simple for end users while also being generally foolproof. You can move the file to another machine, double click on it (opening it as a file:// url) and it'll just work.
I was talking to @batpad and he mentioned that having a directory of files might be convenient in some situations. This would allow for some separation between the original data and the code.
Optionally export data into a folder so the Parquet data can stay in binary form. Note that the output directory then needs to be served, it can't be opened as a file.
The text was updated successfully, but these errors were encountered: