-
-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Utility for constructing Dimensions from Parameters? #1190
Comments
Seems like a very plausible utility, either to just declare kdims from parameters or to declare the entire dynamic map... |
Filtering by precedence would also be useful, so that by default hidden parameters aren't included, but the precedence value can be increased or decreased to get more or fewer widgets. That way there can be filtering that works across a set of Parameterized objects without knowing anything about their internals. |
After some discussion we weren't convinced of the value of such a utility as it seems rather limited. Unless there are any new suggestions, I'm popping this issue off the 1.8 milestone. I suspect we might decide against the idea in future in which case the PR and this issue could then be closed. |
Do we still want this? I really can't see an implementation that's actually going to be useful. In any case I don't think it will happen for 1.9. |
@jbednar I'm happy to close this issue now but also happy to consider any updated proposals you might have in a new issue. Is that ok? |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
An
hv.Dimension
is quite like aparam.Parameter
, in that both establish a named dimension with bounds, and they are often used for the same purpose, e.g. to determine the type of widget and the numerical range covered by that widget (such as a slider). In the code below, the declaredkdims
list is a copy of data already stored and declared on the underlyingparam.Parameterized
objectig.DifferenceOfGaussians
, and it would reduce redundancy and increase generality if those values could simply be looked up on the Parameterized object.So, maybe we could have a utility that will accept a Parameterized object and then return a list of Dimensions for use as kdims, possibly with specified filtering (whitelist and blacklist) on the parameter names? Coupled with #1189, this approach could get rid of all the duplication between the DynamicMap and the DifferenceOfGaussians object, making it possible to use the same code with any such object to give widgets for whatever Parameters it found there.
The text was updated successfully, but these errors were encountered: