Loïc Huder

Great call @bmaranville, I wholly agree. The debounce indeed only makes sense when using providers that make requests for each slice such as H5Grove or HSDS. It only gets in...

Early thoughts when reading this: - `RgbVis` should indeed follow the behaviour of `HeatmapVis`, now that it supports custom axes values - `isIndexAxis` could be renamed to `restrictToIntegers` or something...

The concept of `tickStep` looks promising to me too. I am curious to see if it can remove the need for generation of axis values and/or threshold scales. As for...

No, the closest vis is the `Heatmap` that has the color mapping but without 3d rendering. This is something we might implement in the future if there is enough interest...

> Do you think this is difficult to implement? Depends. In H5Web, honestly yes :sweat_smile: ! We have a lot of components that rely on the postulate that the view...

@kevinxiaomu We have a first implementation in https://github.com/silx-kit/h5web/pull/1303 Before we continue improving it, could you elaborate on your usecase ? For example, would you want to use this surface plot...

The vis is still unfinished so it is not yet released. Sorry

> Upgrading to the latest version of `ariakit` solved the error I was having in the tests. Sweet !

That won't be super helpful since we don't support categorical axis labels, but this is how you would structure your data in a NXData group: [nx_categorial_datasets.zip](https://github.com/silx-kit/h5web/files/11725555/nx_categorial_datasets.zip) Just to give you...

Yep, once I managed to fix the CI :smile: