As I mentioned on the call today, the binding of a control with a variable is made by string holding the variable name, e.g.:
numericParam('variable', min = -19, label = "Numeric value")
However the original param function: https://github.com/att/rcloud.params/blob/8f74f5645e0bd2810930a8ad096bb4bfc87414df/R/rcloud.params.R#L5
accepts the actual variable and then it invokes deparse(substitute(var)) to get its name. I plan to add this to *param functions as well, so the following notation is possible:
numericParam(variable, min = -19, label = "Numeric value")
still a bit of testing is outstanding, especially around UI-to-R value mapping and error handling
*Param functions allow for specifying a 'group' parameter - I will most likely remove this ( it was supposed to group related controls together, but this was before an implementation of a 'paramSet' represented as an HTML form was introduced) and now it became redundant.
gordonwoodhull
commented
5 years ago
@gordonwoodhull this is an early view on the current state of rcloud.params implementation.
For available features and examples please refer to README.md file.
To run rcloud.params changes from the following PR also need to be applied locally:
As mentioned, this is an early view of the implementation, the following are still outstanding:
support for non-busy-waiting forms (https://github.com/att/rcloud.params/issues/12)
As I mentioned on the call today, the binding of a control with a variable is made by string holding the variable name, e.g.:
numericParam('variable', min = -19, label = "Numeric value")However the originalparamfunction: https://github.com/att/rcloud.params/blob/8f74f5645e0bd2810930a8ad096bb4bfc87414df/R/rcloud.params.R#L5 accepts the actual variable and then it invokesdeparse(substitute(var))to get its name. I plan to add this to*paramfunctions as well, so the following notation is possible:numericParam(variable, min = -19, label = "Numeric value")still a bit of testing is outstanding, especially around UI-to-R value mapping and error handling
parameter aliases (https://github.com/att/rcloud.params/issues/6)
*Paramfunctions allow for specifying a 'group' parameter - I will most likely remove this ( it was supposed to group related controls together, but this was before an implementation of a 'paramSet' represented as an HTML form was introduced) and now it became redundant.