|
|
It would be useful to have an official mechanism for running an Exchange script from the UI. While it would be useful to have access to more Exchange methods in UI Ruby scripts, this could act as a stop-gap or cover other use cases where a method needs to remain Exchange-only.
Currently the best way to do this is using Ruby's Open3 module but this has some issues: stdout capture doesn't work, and without fiddling with working directories you can't have Exchange edit the network you've run the script from.
An official mechanism could ensure no other networks are open (avoiding working directory conflicts), and if run by right clicking a model group, it could send the current database + model group as arguments to act as the starting point for the script.
