piet.eeken
Bug in Explorer or Kino?
In the livebook of Explorer I found a probable bug:
input = Kino.Input.text(“d:/livebooks/fossil_fuels”)
filename = Kino.Input.read(input)
DataFrame.to_csv(df, filename)
input gives: d:/livebooks/fossil_fuels without quotes
filename gives: " ".
What is the reason using Kino.Input?
Why not just: DataFrame.to_csv(df, “d:/livebooks/fossil_fuels”)
Most Liked
jonatanklosko
Inputs are a UI element for user to enter a value, so you would do this:
# Cell 1
input = Kino.Input.text(“Path”) # <-- label
# [Renders text input]
# Cell 2
path = Kino.Input.read(input) # <-- read the value of the input field above
Last Post!
piet.eeken
A few weeks later and I tried again. I suddenly did see the input-field. On my screen it was hard to see, the color was almost white.
Maybe it is better to outline the input-field in Kino? Maybe you can tip the makers of Kino, I don’t know them.
Sorry for the troubles. So the livebook on Ten Minutes to Explorer — Explorer v0.7.2
is working perfectly.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex









