Open larshg opened 4 years ago
I'm wondering if it is of interest to move this method and leave it up the user to get clouds from the visualizer and save them using I/O.
Simple to remove dependency Visualizer-> I/O.
The other method returns a pointcloud from vtkPolyData can remain, but maybe move it / rename the IO filename?
I can see that visualizer can also add a ply file directly. Should this maybe be moved to I/O as well?
:+1: Everything sound reasonable. Keep io stuff in io. If VTK is needed, detect it during configuration and compile with it if possible.
I'm wondering if it is of interest to move this method and leave it up the user to get clouds from the visualizer and save them using I/O.
Simple to remove dependency Visualizer-> I/O.
The other method returns a pointcloud from vtkPolyData can remain, but maybe move it / rename the IO filename?
I can see that visualizer can also add a ply file directly. Should this maybe be moved to I/O as well?