Stream support: VTP and VTU writing functions#3297
Conversation
|
I don't see any |
|
Yes. It only affects the writing, so we still need VTK to read the data. Do you want me to add #ifdef directives to filtrate what always work and what needs vtk ? It seems like a good idea nw that you mention it. |
|
If you are no longer using data structure from VTK, I don't see why VTK would be needed at all. So |
We still use vtk structures for reading data, so we still need VTK libs. |
|
The idea is that writing a VTU/VTP file is not too complicated, because we master everything, and we can chose a particular file format, in the set of things allowed by the VTK file format description. But reading VTU/VTP files is another story: one has to be able to read all possible valid VTU/VTP files. That includes at least a full XML parser, the possibility to decode base64, gzip compression, and maybe other things. So we will be:
|
|
Travis reports a license issue: |
…endencies problems. Also fix vtu writer of VTK_io_plugin for polygon meshes.
|
https://travis-ci.org/CGAL/cgal/jobs/436537979#L3618 |
|
We are close: |
|
|
@maxGimeno: why the |
|
There seem to be indentation issues in this PR. |
d67202f to
dc275ec
Compare
|
Successfully tested in https://cgal.geometryfactory.com/CGAL/testsuite/results-4.14-Ic-116.shtml |
…or_vtu-GF Stream support: VTP and VTU writing functions
Summary of Changes
Add functions to write surface meshes, c3t3 and cdt to vtp and vtu format, without using the VTK lib, which avoids having to use intermediary structures.
Release Management