scenebuilder VS Pluto.jl

SceneBuilder, good luck!

Can't argue with that, but to me it seems that things have substantially deteriorated since desktop GUIs fell out of fashion. Maybe that tells you more about my age than about the state of the art, but in the 90's one could "learn" GUI programming in about 30min in a RAD tool by throwing controls in containers and implementing callback functions in "direct style" for the event (Qt , swing, Java/ScalaFX, Gtk, Forms, delphi, …), or do all that in code instead, with objects representing components and inheritance/OOP doing wonders to encapsulate state, expose a type-safe discoverable API, and offer customizability through members override. Entire generations of corporate monks made visually and functionally convincing business apps with VBA in an afternoon for instance.

Yes it does[1] and it works on Desktop, mobile and web.

JavaFX has SceneBuilder[2] which also fit the description but for some reason, it never caught on. Gluon seems to have that work not only on desktop, but also on mobile.

[1] https://docs.flutter.dev/development/tools/devtools/overview

[2] https://gluonhq.com/products/scene-builder/

JavaFX (Desktop) -> Use Scene Builder standalone from Gluon. https://gluonhq.com/products/scene-builder/

Additionally you can learn JavaFX for desktop applications. JavaFX with Gluon Scene Builder (https://gluonhq.com/products/scene-builder/ ).

SceneBuilder

Just run it from source until you figure it out

I thought that notebook based development and package based development were diametrically opposed in the past, but Pluto.jl notebooks have changed my mind about this.

A Pluto.jl notebook is a human readable Julia source file. The Pluto.jl package is itself developed via Pluto.jl notebooks.

https://github.com/fonsp/Pluto.jl

Also, the VSCode Julia plugin tooling has really expanded in functionality and usability for me in the past year. The integrated debugging took some work to setup, but is fast enough to drop into a local frame.

https://code.visualstudio.com/docs/languages/julia

Julia is the first language I have achieved full life cycle integration between exploratory code to sharable package. It even runs quite well on my Android. 2023 is the first year I was able to solve a differential equation or render a 3D surface from a calculated mesh with the hardware in my pocket.

Re Julia there is also pluto.jl that is another notebook-like environment for julia. It's been a few years since I played with it but it looked cool, for example it handles state differently so you don't get into the same messes as with ipython notebooks. https://plutojl.org/

For this, Notebooks are often used. Julia offers a uniquely nice and interactive Pluto notebook for the web https://github.com/fonsp/Pluto.jl

I believe this is what Pluto sets out to do for Julia.

I used it as part of the “Computational Thinking” with Julia course a year or two back. Even then the beta software was very good and some of the demos the Pluto dev showed were nothing short of amazing

https://plutojl.org/

I think what you want is Pluto!

I like how Pluto.jl handles this:

> Pluto offers an environment where changed code takes effect instantly and where deleted code leaves no trace. Unlike Jupyter or Matlab, there is no mutable workspace, but rather, an important guarantee:

> At any instant, the program state is completely described by the code you see.

[1] https://github.com/fonsp/Pluto.jl