livebook

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

You can have a look at the code: https://GitHub.com/livebook-dev/livebook/tree/main/app_bundl...

I think when LiveBook desktop[1] is ready, it's going to become a lot more compelling. [1]https://github.com/livebook-dev/livebook#desktop-app

I'm in elixir land - but have a look at https://github.com/elixir-desktop - they even have an ios app in the app store.. basically wxwidgets comes with a webview, and that one is loaded up - and everything is packaged as an app - so you can use phoenix (liveview), or even react or anything to your liking.. believe certain improvements were made to OTP 25, so multiple things will land soon - even livebook https://github.com/livebook-dev/livebook are aiming at shipping a native app..