couple of comments ;-)

[jourdain]

Instead of using npm start, you can serve the content of www by adding --content /path/to/www to the pvpython command line.

Moreover, since the content will be served from the paraview http server the endpoint/sessionURL can be automatically guessed so the config can be empty when given to the smart connect.

Inside your package.json, since you added kw-web-suite you don't need any build tools such as webpack as kw-web-suite aims to be similar to apt-get install build-essential for linux. So your devDependencies could only contains kw-web-suite.

You should replace

• import RemoteRenderer from 'paraviewweb/src/NativeUI/Canvas/RemoteRenderer'; with
• import VtkRenderer from 'paraviewweb/src/NativeUI/Renderers/VtkRenderer';

But for that you will have to:

• Add in the predefined protocol of your client VtkImageDelivery
• Instantiate the renderer as follow const renderer = VtkRenderer.newInstance({ client: model.pvwClient });
• You will be missing the onImageReady method
• In your python add the self.getApplication().InvokeEvent('UpdateEvent') call each time you want the client to have a new rendered image.

[nodeCodeNinja]

@jourdain - What are the differences between RemoteRenderer and VtkRenderer Is is to use self.getApplication().InvokeEvent('UpdateEvent')

[jourdain]

The RemoteRenderer was the first implementation where the client request each image while the VtkRenderer expect a push from the server.

[nodeCodeNinja]

Great!

Apart from above, I had to add self.registerVtkWebProtocol(pv_protocols.ParaViewWebPublishImageDelivery(decode=False))

It works great with realtime push from backend without a page refresh to see updated image

[Morasta]

@nodeCodeNinja : do you have a complete example of the changes you made to make realtime pushes work?