21–30 of 63 posts
Earlier quoted context omitted.
Don't leave us hanging! What did you use instead 3 weeks ago?
Wails https://wails.io >. I wanted to use Go but wasn't as familiar with native UI as with HTML/CSS/JS, I tried out most of the other popular Go UI frameworks too though they didn't feel as comfortable to use as Spot's React-like model. Wails is still pretty epic as well though.
If only I had known about this (or judging by commit history, if it existed) ~3 weeks ago. I've been saying for ages that either React ported to Go or a React-like framework for Go would be an incredible development experience, so this looks perfect (I used to be a big hater of React.js until I was enlightened by React.lua).
Eventually found a way to do something similar using just the standard Go html/template.
I’ve written about the implementation here:
https://www.sheshbabu.com/posts/react-like-composition-using...
I applaud your effort, but cross plattform with no Windows support?
Cool! What does building for cross platform look like? Would love if there was a command that produced my MacOs .app and Windows exe without me having to dive into package management/containers/signing headaches per platform.
Fltk supports windows. Will you be using another solution and that’s why u don’t support windows yet?
My (low prio, though) goal is to implement a Win32-based backend, though, the first step is done: https://github.com/roblillack/spot/pull/4
I'm curious to hear your take on this: what's the advantage of following the virtual control tree approach compared to instead updating directly the controls that are displayed to the user?
With the reactive approach you are able to write a single rendering function that describes the interface for any given state and the framework takes care of the rest (when to call that function, what "input" to give it).
It's just way easier to wrap my head around this and after working with React it is hard to go back. Hence the experiment to see if something comparable could be done in Go.