livebook

For me, the best about Tauri is that: - We can embed an existing application using a sidecar [1]. - Now, we can also use Elixir in the backend, embed the BEAM, and deliver a single binary, see ElixirKit [2]. As far as I know, LiveBook Desktop [3] is using Tauri for building binaries for MacOS and Windows. If Tauri works for the Elixir team, I think it works for me too. Also, I know that Tauri is not bullet proof. WebView can be limited for some use cases, see [4]. There is some effort to use CEF to mitigate those problems, though [5]. I'd like to know how Deno Desktop compares with Tauri in this context. I know it is a new product, not sure if we could bundle an existing binary in Deno Desktop, like in ElixirKit. [1] https://v2.tauri.app/develop/sidecar/ [2] https://elixirkit.hexdocs.pm/tauri.html [3] https://github.com/livebook-dev/liveb

Livebook actually uses state reducers as described here[1]. Except for cell content. There it uses Operational Transformation. The source code[2] is really instructional and easy to understand. I highly recommend to look into it :) [1] https://github.com/jonatanklosko/notebooks/blob/main/article... [2] https://github.com/livebook-dev/livebook/blob/main/lib/liveb...

For linux the easiest way to download livebook is with docker [1] or maybe with fly.io [2]. Installing it directly is a bit complicated if you are not familiar with it. I wish linux also had Desktop app like mac. [1]: https://github.com/livebook-dev/livebook#docker [2]: https://fly.io/launch/livebook

The pipes are really very nice. They are actually even nicer under Livebook: https://livebook.dev/ It can let you drag-drop reorder, enable/disable, steps in a pipeline: https://github.com/livebook-dev/livebook/blob/main/lib/liveb... It is really wild.

Things that are in our roadmap in relation to our data vision: * Data management within your notebook (https://github.com/livebook-dev/livebook/issues/1604) - we want you to be able to link files, urls, and object storages to your notebook and automatically manage/download it * We want to make it easier to build visualizations (even easier than the current Chart smart cell) and also be able to filter a dataframe by selecting a visualization: https://github.com/livebook-dev/livebook/issues/1545 We have other ideas, such as making SQL a more prominent citizen in Livebook and be able to build a custom canvas as your work on your notebook, but those will likely take longer to realize.

The documentation is a bit hard to find. It seems to be here? https://github.com/livebook-dev/livebook/blob/main/lib/liveb...

Generally speaking, if it can be done in the client, it should be done in the client. Phoenix.LiveView.JS aims to tackle the obvious cases but it also documents a pattern that I tend to use a lot in my apps: https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.JS.htm... The pattern above has a benefit that the dispatch still comes from Phoenix, so you are not relying on IDs or query selectors to attach functionality. You can see how we use it in Livebook here: https://github.com/livebook-dev/livebook/blob/main/assets/js.... However, if the callbacks get too complex, then you may indeed want to test them via headless browsers.

Right, so our goal was to allow configuring the bundle with app icons etc and importantly custom URL schemes and file types [1]. And then macOS- [2] and Windows- [3] specific launchers capture the "open file" and "open url" events and trigger the Elixir side of things. Another reason for native launchers is if for any reason we couldn't start the Elixir side, we want to let the user know that something went wrong and point to logs. (We have that on Mac and will have on Windows very soon.) [1]: https://github.com/livebook-dev/livebook/blob/920f70817efbac... [2]: https://github.com/livebook-dev/livebook/blob/920f70817efbac... [3]: https://github.com/livebook-dev/livebook/blob/920f70817efbac...

Not as a downloadable desktop app, yet. You can run it in docker[1]. [1]https://github.com/livebook-dev/livebook#docker]

No problem! The pr here[1] is also instructive, and here is the one for windows[2]. It seems similar-ish. [1] https://github.com/livebook-dev/livebook/pull/865/files [2] https://github.com/livebook-dev/livebook/pull/1032/files

Sorry about that! A bug report at https://github.com/livebook-dev/livebook/issues/new would be very appreciated, especially with relevant parts from ~/Library/Logs/Livebook.log.

I, too, am interested but I'm not terribly literate in elixir yet. I am aware that you can compile executables in elixir with a release command but I'd be curious to hear more about (or at least be pointed to the specific spots in the code) how the bundling was done to give you a discrete application per platform, with app icon and everything. Having a script that opens a web browser pages is simple enough, but the extra sugar on top to wrap in an app bundle that shows up in your task bar or dock is something I am very curious about. EDIT: Someone further down the thread linked to a more specific place and that led me to the macos.ex file[1] (which is what I was most interested in, being on macOS myself. It looks like at least in the case of macOS it will build the bundle by hand, template in enough swift code to build the application, si

It's used for the desktop app, as you can see here[1]. [1] https://github.com/livebook-dev/livebook/blob/355527f7e8034e...

No Linux download :-( Nevertheless it's fairly easy to install[1]. If you have docker, you can just run the image to try it out: docker run -p 8080:8080 -p 8081:8081 --pull always livebook/livebook You may want to configure some things, so check out the options[2].: If you want a "native" install, after you have elixir installed you can use mix escript.install hex livebook and start it with livebook server Check out the readme for more configuration options[1] [1]: https://github.com/livebook-dev/livebook#installation [2]: https://github.com/livebook-dev/livebook#docker