Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ParaView serialization #2

Open
9 tasks
jourdain opened this issue Apr 17, 2024 · 4 comments
Open
9 tasks

ParaView serialization #2

jourdain opened this issue Apr 17, 2024 · 4 comments

Comments

@jourdain
Copy link
Collaborator

Missing serializer for:

  • vtkPVLODActor
  • vtkOpenGLPointGaussianMapper
  • vtkPVGridAxes3DActor
  • vtkPVRendererCuller
  • vtkCameraPass
  • vtkLabeledDataMapper
  • vtkPVAxesActor
  • vtkCoordinate
  • vtkPVInteractorStyle
@jourdain
Copy link
Collaborator Author

jourdain commented Apr 17, 2024

@jspanchu
Copy link
Member

Okay, that is quite smaller list than I expected.

@jourdain
Copy link
Collaborator Author

That is just with a cone... But indeed not too bad... Now the question is how can we handle those since they are not part of VTK.

@jspanchu
Copy link
Member

Now the question is how can we handle those since they are not part of VTK.

For this purpose, I've added basic mechanism in vtkObjectManager::InitializeExtensionModuleHandlers( const std::vector<RegistrarType>& registrars) that is capable of loading serialization handlers from libraries external to VTK. Here RegistrarType is a function pointer. Now, the remaining task is to somehow get the extension library's registrar function pointers in Python/JS and send them to vtkObjectManager in python world and vtkWasmSceneManager in wasm world.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants