USE CASE: calling go-callvis from a Makefile to non-interactively generate an output image of dot visualization
The examples page shows usage such as
go-callvis <opts> | dot -Tpng -o output.png
However this calling style still seems to launch the web browser with output rather than just outputting a dot PNG file, making it unsuitable for use in scripts or makefiles. Piping to 'dot' util as in the examples appears not to work as go-callvis doesn't output suitable data to stdout.
EDIT: I see that while the program is running, the output is written to /tmp/go-callvis_export.svg. Basically it would be good if this were specifiable via a new option like '-output' to give a custom path, and if -skipbrowser or the presence of -output would prevent launching the web browser and have go-callvis exit after generating the SVG.
I'll work on a patch to do this and submit a pull request.
USE CASE: calling go-callvis from a Makefile to non-interactively generate an output image of dot visualization
The examples page shows usage such as
go-callvis <opts> | dot -Tpng -o output.png
However this calling style still seems to launch the web browser with output rather than just outputting a dot PNG file, making it unsuitable for use in scripts or makefiles. Piping to 'dot' util as in the examples appears not to work as go-callvis doesn't output suitable data to stdout.
EDIT: I see that while the program is running, the output is written to /tmp/go-callvis_export.svg. Basically it would be good if this were specifiable via a new option like '-output' to give a custom path, and if -skipbrowser or the presence of -output would prevent launching the web browser and have go-callvis exit after generating the SVG.
I'll work on a patch to do this and submit a pull request.