A way to bind procedure files into an experiment?
Thu, 02/10/2022 - 05:51 am
I am wishing for a way to "bind together" procedure files into an experiment file so that, when I distribute the experiment itself (e.g. as a demo package), users do not have to have the corresponding procedure files installed locally. Using the analogy with #pragma directives, I would see this ...
#bind <procedure file name>
At compile, the directive would load the procedure file (from User's Procedures) and "bind" it into the experiment by storing it within the experiment in some manner. At future compiles, the directive would run the procedure file from the embedded version, ignoring any external file by that name.
I have utility procedure files that layout graphs + panels, that take snapshots into notebooks, and that scroll through traces. The tragedy for me is that, every time I develop an experiment that I would like to share with students or colleagues, I have to copy + paste the utility functions into my experiment procedure window.
I suspect that this request may also dovetail with requests for ways to make experiments "stand alone".