Philipp Rudiger

This is probably a pre-requisite to get the above mentioned workflows working well: https://github.com/holoviz/holoviews/pull/6061

Okay just to capture what I think needs to happen to support this workflow well. Currently the cost of the operation can be broken down into `N*slicing + N*downsampling` where...

I do think this is important, often you will create this view by grouping a dataset by some dimension and those operations will produce an NdOverlay with the values along...

>Sounds like something else that could go into the Dimension properties once that is implemented... We already have range and soft_range so I don't think anything new is needed. Just...

@jbednar Any opinion on this? I think it would be nice to offer hard bounds on the axes, should we say that if you explicitly set an ``Dimension`` ``range`` that...

>I think I'd always want such bounds, but can't be sure until I experience it. I think so too, but not actually having used it I don't know either. I...

Other suggestions: ```python import holoviews as hv import dask.array as da import panel as pn sx = sy = 1000 arr = da.random.random((sx, sy)) img = hv.Image((range(sx), range(sy), arr)) fig...

Agree that this should work, for the time being you should be able to work around this by applying the linked selections to each component individually and only composing them...

>Do you know of any examples that expound upon that? You can use it like this: ```python ls = hv.link_selections.instance() tiles * ls(el1) + ls(el2) ```

So this seems to work: ```python from panel.io.notebook import load_notebook load_notebook() hv.Curve([1, 2, 3]) ``` For some reason the `load_notebook` call in `holoviews.plotting.renderer.Renderer._render_ipywidget` isn't being executed.