Sebastien Jourdain (Kitware)

Those two features are not yet implemented and would require so add-on on the UI side.

You may want to report your issue [here](https://discourse.paraview.org/) while also explaining more what you did? (version of PV, command line or double clicked on the paraview.exe). If I'm not mistaken,...

The rewrite for cross platform could be good. For the `svg-sprite-loader` it might be trickier as some logic may be different in the new loader and make all the svg...

Updating the build process of the library should fix the issue. PR are welcome, but that project is not maintained anymore.

Did you go through [that documentation](http://kitware.github.io/paraviewweb/docs/launching_examples.html)? It might help you get a better grasp of each part. The big picture is that you should always connect to Apache (usually on...

One inconsistency 1. Launcher config `"sessionURL" : "ws://paraview:80/proxy?sessionId=${id}&path=ws",` 2. Apache config `` `:80 !== :8090` which means that the client will have no way to reach back to its pvw...

The issue is then in your launcher config ==> `"sessionURL" : "ws://localhost:8090/proxy?sessionId=${id}&path=ws",`

I don't understand your question about the index.html.

You don't need to edit any html at all to make it work.

The user should NOT be redirected to any other port as Apache will do the rooting internally. The endpoint on /paraview only expect a POST request and therefore is not...