- this commit adds ability to view tracing information that is emitted from `vtkDeserializer`, `vtkSerializer` and `vtkObjectManager` by configuring a log verbosity. The verbosity can be set either as an environment variable or directly on the object manager, serializer and deserializer.
- for wasm, new methods are provided in the wasm scene manager bindings. these methods let you pass in strings like "WARNING", "INFO", etc.

Kitware Robot authored 5 months ago and Ben Boeckel committed 5 months ago

Also use C++17 syntax rules as the next release expects to use C++17.

- this method helps serialize a single object and it's dependencies into the context. the new state can be retrieved via `GetState(id)`
- you don't need to call `UpdateStatesFromObjects`  which traverses the entire tree.

- this method is useful to update a single object's properties from a state.
- you don't need to call UpdateObjectsFromStates which traverses the
  entire tree.

- This is useful when attempting to capture the state of objects that
  were constructed through deserialization in wasm.
- Also adds a simple unit test which changes window name of a
  render window after deserialization, updates the
  state and verifies state reflects the change.

Jaswant Panchumarti (Kitware) authored 9 months ago and Jaswant Panchumarti (Kitware) committed 9 months ago

- Serialization code for vtkGlyph3DMapper and vtkOpenGLGlyph3DMapper is autogenerated

Jaswant Panchumarti (Kitware) authored 9 months ago and Jaswant Panchumarti (Kitware) committed 9 months ago

- vtkCompositeDataDisplayAttributes is serialized with helper code written by hand
- serialization code for vtkCompositePolyDataMapper is autogenerated

Jaswant Panchumarti (Kitware) authored 9 months ago and Jaswant Panchumarti (Kitware) committed 9 months ago

- vtkMultiBlockDataSet, vtkPartitionedDataSetCollection and vtkPartitionedDataSet are serialized with helper code written by hand
- Serialization code for vtkMultiPieceDataSet, vtkDataObjectTree, vtkCompositeDataSet is autogenerated.

- Enables automated marshalling for some classes in the following modules
  1. ChartsCore
  2. RenderingContext2D
  3. RenderingLabel
  4. ViewsContext2D
  5. ViewsCore
- Enables automated marshalling for additional classes in the following
modules
  1. CommonExecutionModel
  2. InteractionWidgets
  3. RenderingCore
  4. RenderingOpenGL2

- Objects created when serializing properties through RHS getter function are kept alive by the context.
- They will get cleaned up by vtkObjectManager when unused objects get pruned.

- include the relevant module.h headers of the optional module which provides factory overrides  in vtkWasmSceneManager.h so that they are registered with the vtkObjectFactory
-  call `vtk_module_autoinit` with the optional modules in cmake.

- Add new `INCLUDE_MARSHAL` argument in `vtk.module` that opts in
  the module for marshalling and use with `vtkObjectManager`.
- Add new `VTK_WRAP_SERIALIZATION` CMake option
- Add new `ENABLE_MARSHALLING` option for `vtk_module_build`.
- When marshalling is enabled and a `vtk.module` has the
  `INCLUDE_MARSHAL` argument, serialization code and registrar code
    will be generated for that module.
- Add new `vtk_module_serdes` CMake function to generate serialization
  sources for a module.
- The serialization registrar for each module will be generated
  from the `CMake/vtkSerializationLibraryRegistrar.h.in` template
- Add marshalling support in build system
- Add new SerializationManager module with `vtkObjectManager` class.
- `vtkObjectManager` is meant to be the user-facing class to track
  objects, their states and data arrays hashed in the form of blobs
  to minimize the number of copies of point coordinates, cell arrays,
  scalars, etc.
- Add new `vtkSerializer`, `vtkDeserializer` and `vtkMarshalContext` classes
  to help with (de)serialization and tracking object states. This is
  internally used by `vtkObjectManager`.