High Level Overview of ipyparaview issues (dashboard issue)

[banesullivan]

This issue outlines the relevant issues in Kitware/ipyparaview

• Should we talk to NVIDIA about who is maintaining ipyparaview moving forward?
• Implement more camera models (at least track ball) to improve user interface. See https://github.com/Kitware/ipyparaview/issues/2
• Fix widgets in JupyterLab. See https://github.com/Kitware/ipyparaview/issues/5
• Evaluate what a refactor would look like and how it could be impactful. See https://github.com/Kitware/ipyparaview/issues/6
• Build ParaView in a way that registers the VTK python bindings with conda. See https://github.com/Kitware/ipyparaview/issues/8

[aashish24]

• Should we talk to NVIDIA about who is maintaining ipyparaview moving forward?

Kitware is responsible to maintain ipyparaview moving forward as per our last meeting with NVIDIA

• Implement more camera models (at least track ball) to improve user interface. See Kitware/ipyparaview#2
• Fix widgets in JupyterLab. See Kitware/ipyparaview#5

This is probably is higher priority from our point of view.

• Evaluate what a refactor would look like and how it could be impactful. See Kitware/ipyparaview#6

• refactoring will make it so that we can use VTK or ParaView backend?
• itkwidgets will be a separate path but can we use it as one of the options given a config?
• ideally we want a system that can do client side or server side rendering given a config option either at build/install/run time, how it is done could vary.

• Build ParaView in a way that registers the VTK python bindings with conda. See Kitware/ipyparaview#8