The global constants are confusing and opaque. Creating them in the "publish" window seems a bit strange. Once they are created, they are not visible anywhere so it is unclear to the user if they exist or not.
There are 2 issues:
1) We need a way to specify the parameters that will be visible when the model is published.
2) In some cases, users find they have some value that needs to be used in many nodes. We need to avoid having to create lots of wires for this.
For the first point, we could ask the user to select two nodes when they publish: input node and output node. Input node will be used to identify all the input parameters to display in the viewer. Output node will be what is shown as the output.
For the second point we could rely on user defined functions, which can be called from any procedure.
The global constants are confusing and opaque. Creating them in the "publish" window seems a bit strange. Once they are created, they are not visible anywhere so it is unclear to the user if they exist or not.
There are 2 issues:
1) We need a way to specify the parameters that will be visible when the model is published.
2) In some cases, users find they have some value that needs to be used in many nodes. We need to avoid having to create lots of wires for this.
For the first point, we could ask the user to select two nodes when they publish: input node and output node. Input node will be used to identify all the input parameters to display in the viewer. Output node will be what is shown as the output.
For the second point we could rely on user defined functions, which can be called from any procedure.