kino
kino copied to clipboard
Client-driven interactive widgets for Livebook
Currently payloads are serialized on the Livebook side (`LivebookWeb.JSViewChannel`), so structs from dependencies are not supported.  One way to address this is to serialize before sending messages to Livebook...
We can look at a binary and if it looks like an image, we can automatically show it as said image.
It should also be supported within branched sections and only interrupt that branch. @jonatanklosko mentioned that Process.exit may be enough.
When using `Kino.DataTable` in livebook, it will only show 10 rows at a time. This should be configurable. As far as I can tell it is hardcoded to 10 here....
There is an [excellent paper](https://arxiv.org/abs/2009.10643) and [talk on the matter](https://m.youtube.com/watch?v=Nnpll1Srmbs&list=PLkTCpJUe8hMwLV4miGQbqiqpAYXy4XfN-). Examples we want to consider in the future are: 1. API widget - a widget to the API requests which...
There are some ideas flying around: 1. [x] Support Nx.Tensor in Kino.Image by using a custom content type that is loaded into a canvas 2. [ ] Have a canvas...
This PR adds file type to `Kino.Input`. This PR is related to https://github.com/livebook-dev/livebook/pull/1207.
We can support an additional option in `Kino.Frame.render/2` for targeting a specific user. Events generally have an `origin` field that represents the user, so we would use it as the...
We may want to wait until the official release, but doesn't hurt to have the implementation around :) https://user-images.githubusercontent.com/17034772/130112186-b4ebcea6-821a-4623-ac44-62fe66384e6b.mp4
The cell Will be an editor but it will also support drag and dropping a file. We will use NimbleCSV for parsing. Although we will most likely need to add...