Sebastien Jourdain (Kitware)

The initial `100` (min) was coming from my manual range definition inside ParaView when exporting the scene. So the loading is behaving the way we expect. Just the "Reset" seems...

LightViz has not been updated to fix ParaView 5.8 imports. If you want to use it, you can fix them by following what was done [here](https://github.com/Kitware/paraview-lite/blob/master/server/lite_protocols.py#L12-L33).

See https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/Offscreen.html but that was added after 5.4.1. So either you don't use that argument or you use a newer version of ParaView. Ideally you should use LightViz that is...

Update ParaViewWeb but skip kw-web-suite since the change is a breaking one (major 5->6). That means the build system changed a lot while it should not prevent your from building...

Meaningful error: `You may need an appropriate loader to handle this file type. (*.svg)` Way to solve it: Learn how Webpack works. Then use existing code/example to ease the process....

I'm not trying to be rude, I'm just pointing out that the issue tracker on ParaViewWeb or LightViz are not meant for general JavaScript / Webpack question. I agree that...

Not yet as vtk-js does not have any of those filters available. For that you will still need a server unless you precompute all possible geometries for all the filter...

This is weird, 40MB is nothing unless the server never free memory. Do you have context file? Looking at the code I see a typo [here](https://github.com/Kitware/light-viz/blob/master/server/light_viz_protocols.py#L207-L208).

It is possible to deploy for multi-server setup. The current limitation is related to the fact that the dataset listing is expected to be on the machine that do the...

Definitely yes, except that we didn't put any UI to make such network call.