Are the prompts for 'configuration' only? If so you could still stick it on a server, but take some querystring params for the options (built into a web page UI), then do the major work server side.
Another option... perform the interaction over TCP instead of HTTP - now you can use netcat to demo it.
The WASM thing is absolutely overkill, with you there 100%.
Are the prompts for 'configuration' only?
Not really - the prompts are the main event. It builds a branching tree of prompts from the input file provided, and can refer to previously received responses.
The "real" option would be to ditch text prompts and build graphical widgets, which sounds fun, too, but not a one-day thing.
That might be exactly the ticket - no real need to translate to Rust, I might just start with your Go template if you don't mind, that looks like less friction.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yup,
curl
won't cut it.Are the prompts for 'configuration' only? If so you could still stick it on a server, but take some querystring params for the options (built into a web page UI), then do the major work server side.
Another option... perform the interaction over TCP instead of HTTP - now you can use
netcat
to demo it.(I like this idea so much I almost want to write a 'framework' for it...)
The WASM thing is absolutely overkill, with you there 100%.
Not really - the prompts are the main event. It builds a branching tree of prompts from the input file provided, and can refer to previously received responses.
The "real" option would be to ditch text prompts and build graphical widgets, which sounds fun, too, but not a one-day thing.
This definitely sounds like it fits. I've never mucked about with TCP before but I don't think there's anything in my way conceptually, at least.
I've just scrapped around with this in Go - I'm sure you can convert to Rust with ease - using
cowsay
as the target command line app:/thread
Above and beyond, David, thanks for the sample!
That might be exactly the ticket - no real need to translate to Rust, I might just start with your Go template if you don't mind, that looks like less friction.