As planned, I've just implemented an "execute" command which runs a given operating system command in a separate process (opt. providing some given input) and returning exit code, regular output and error messages.
So far, it has been tested on my Mac only - since I do not own any Windows machine. As usual (for cross-platform solutions running OS commands) it's a bit "hacky" - but it allows Wyldcard to be used as a "front-end" for commands and/or network services (when using curl as the command to be run)
Perhaps, you may find it useful as well...
With greetings from Böblingen (next to Sindelfingen, where the Daimler cars are built),
As planned, I've just implemented an "execute" command which runs a given operating system command in a separate process (opt. providing some given input) and returning exit code, regular output and error messages.
Documentation can be found in https://github.com/rozek/wyldcard/wiki.
So far, it has been tested on my Mac only - since I do not own any Windows machine. As usual (for cross-platform solutions running OS commands) it's a bit "hacky" - but it allows Wyldcard to be used as a "front-end" for commands and/or network services (when using
curlas the command to be run)Perhaps, you may find it useful as well...
With greetings from Böblingen (next to Sindelfingen, where the Daimler cars are built),
Andreas Rozek