> While other Nim GUI are mostly unknown territory. Unfortunately true. Though I've really enjoyed hacking away on Fidget & Fidgetty. There's lot of potential, but _also_ lots of work and never ending details. I'd really like to be able to re-use the native text input boxes like the browsers (used to?) do. Text input handling is such a pain. :/
> I experiment with such approach, something like Elixir Phoenix LiveView + > React.JS in Nim , but eventually discarded it, as it's simpler to just use > Svelte & TypeScript. LiveView is fantastic! Well except for the web part. I think a library like that for Nim would be great. Alternatively a Clojure style seemless front-end / back-end style library would be equally good. Though it seems one hasn't really taken off on the Nim front? > network latency is zero and bandwidth unlimited, so you can just mirror every > single change and send back and forth between Nim Process and Web Browser > every single event. In theory, Fidget's rendering engine(s) and its user facing API could be split and the data sent over a binary protocol. Fidget essentially builds up a tree of dom-like nodes. They're simpler than dom nodes though so serializing them wouldn't seem to be infeasible assuming appropriate caching for images/fonts/strings. I've toyed with the concept of doing that in Fidggety as a possible way to have a Nim(C) renderer and a Nim(VM) / Nim(JS) frontend for rapid development. It'd probably be possible to mock up in a weekend. Ok... a long 3 day weekend. ;)
