You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pn.panel(obj) function is really useful for creating an appropriate Pane type from a given obj without having to think very deeply about the space of possible Panes, as long as what's returned is close enough to what we want.
Can we have something like that for widgets, i.e. pn.widget(obj), constructing an appropriate widget type for an object in the same way pn.interact does for function arguments, but in a standalone way that can be used in an example like the following? Here I'm assuming a user is starting with some code that works for specific lon, lat values, and wants to add widgets for those:
I'm not sure how this mechanism would intersect with the magic that hvPlot already does with pn.widgets.DiscreteSlider to figure out the discrete set of objects; clearly being able to auto-discover that sort of information is really helpful, but I don't know the limits on how to do that practically. In any case just getting any sort of widget is a great start, because then people have a working app and can go from there...
The text was updated successfully, but these errors were encountered:
The
pn.panel(obj)
function is really useful for creating an appropriate Pane type from a givenobj
without having to think very deeply about the space of possible Panes, as long as what's returned is close enough to what we want.Can we have something like that for widgets, i.e.
pn.widget(obj)
, constructing an appropriate widget type for an object in the same waypn.interact
does for function arguments, but in a standalone way that can be used in an example like the following? Here I'm assuming a user is starting with some code that works for specific lon, lat values, and wants to add widgets for those:Right now they need to know the right magic to instantiate a widget first:
But it would be great if they could just use the widget abbreviations described at https://panel.holoviz.org/user_guide/Interact.html to construct a suitable widget:
I'm not sure how this mechanism would intersect with the magic that hvPlot already does with
pn.widgets.DiscreteSlider
to figure out the discrete set of objects; clearly being able to auto-discover that sort of information is really helpful, but I don't know the limits on how to do that practically. In any case just getting any sort of widget is a great start, because then people have a working app and can go from there...The text was updated successfully, but these errors were encountered: