-
Notifications
You must be signed in to change notification settings - Fork 3
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
Saving file directory is hard-coded by the relative path in the code #106
Comments
Current research:
Possible temporary soln
|
when this is solved docs/source/wiggum_app.rst needs to also be updated to reflect this changed |
If we get this one solved, we can submit Wiggum to pipy, but if this is not solved, we can't because Wiggum can only currently work if run from the same directory as the data, which is complicated. We might be able to come up with another workaround set of instructions for how to launch the app so that it can work without being launched in the code directory, but one of these needs to happen before submitting it to pipy makes sense. |
these can help for data we provide, but not for use-provided data https://setuptools.readthedocs.io/en/latest/setuptools.html#including-data-files |
This issue captures multiple related problems:
|
Tried flask.send_file https://community.plotly.com/t/allowing-users-to-download-csv-on-click/5550, but the function doesn't send file to anyplace. |
I added code under 'save' action: Since os.path.join(directory,data_csv) doesn't give me a correct path, I used a hard-coded file path instead. |
We need to find a better way for the saving path.
JS doesn't provide a way to browser a folder dialog.
The text was updated successfully, but these errors were encountered: