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 multiple input types #321
Comments
Any plans for select and sliders? Here's an example notebook controlling some inference options using both: https://colab.research.google.com/github/tensorflow/lucid/blob/master/notebooks/differentiable-parameterizations/appendix/infinite_patterns.ipynb |
@seanmor5 added to the list |
Colour selection would be cool for customising VegaLite graphs, and the HTML input type is well supported so probably no need to do anything custom on the frontend side: https://caniuse.com/input-color DateTime comes to mind too, though I don't have an immediate use case for that |
Added color to the list. A PR is also welcome! |
to the slider the return must be integer and checkbox/toogle must be boolean? |
We use IO.gets for both and they always return strings. For sliders, it should be the integer as a string, not different from number. For checkbox, let’s go with true/false for now. |
Any thoughts on using file inputs just to store the path to a selected file without itself doing any reading/streaming? Then the Elixir code could access that file using normal File functions however it makes sense to in the live book. I think that’d export sensibly too - if you have the same file on disk then it’ll just work, if you don’t then you can update the path variable to wherever you have your input file. |
@mcintyre94 that would work for local deployments on livebook but not server ones. |
@josevalim Ah got you. Would the expected behaviour for a server deployment be that you can upload a local file then? I'm guessing this would be read-only too? |
Yeah, like a regular file upload. It may make sense to optimize this case that you mentioned but I am not quite sure how to handle it yet. |
We want to support:
Which other inputs do you need? Can you please describe your use case?
The text was updated successfully, but these errors were encountered: