COLLADA .dae file format may be desirable because it's a flexible, complete format.

faerietree / universal_prototyping_kit

UniProKit by open source ecology.

0 stars 0 forks source link

COLLADA .dae file format may be desirable because it's a flexible, complete format. #13

Open faerietree opened 8 years ago

faerietree commented 8 years ago

Does it make sense to add the format directly as .dae?

Which leads to the question if any file should be provided, because it can be generated on the fly: Does it make sense to list any format other than the source .blend?

faerietree commented 8 years ago

Currently .igs, .stp are provided for redundancy. One or the other often is provided.

.blend is the source. Its file size is of the same magnitude as e.g. STL. See also #6.

On modification (check hash?), .igs, .stp may be created using https://github.com/faerietree/freecad_convert.

faerietree commented 8 years ago

While .obj is compact, at the next throng we may need to consider no longer maintain (not remove) all .stp, .igs and .obj files.

Reasons:

Reduce workload.
Reduce redundancy.
To accelerate development (e.g. maintaining .dae may be of direct benefit for the virtual time machine).
The FreeCAD convert project can generate these files on the fly.
There likely are no contributors that are willing to stick to the specific standards and use a UNIX operating system for development while at the same time not using blender or freecad. (If using blender or freecad, then .stp, .igs, .obj are not required.)

Likely only .dae (virtual time machine), .stl (3D printing) will be maintained next to the .blend development files.

For working with FreeCAD, parts need be converted on the fly back and forth which requires a solid bidirectionally loss-less converter.

For OpenFOAM the mesh generators do exist and support .stl.

faerietree commented 8 years ago

Today's throng has decided to remove the files, especially as the world development strategy is currently still evolving.

The respective producer companies et alia can still fork the repositories and add the files if they ever were to want to manage their part files in a git version control system.

The last years have more and more shown that projects on the net explode, spread, turn into chaos and become inconsistent (see blender addons entropy and broken state despite many people's efforts, including the worlddevelopment gather, link shell script). Noone other than the respective authors will ever tidy up projects especially of special tools like blender which often is deliberately labeled as minor for engineering and which requires special knowledge.

This means worlddevelopment does not maintain files other than the .blend source files, potentially motivating people to use the open source toolchain to get a part ready for e.g. 3D printing or OpenFOAM.