STEP exchange files are plaintext but there isn't any guarantee that the position of stuff is preserved after making a change.
Re:Code CAD – Use code to create CAD models
by TaylorAlexander on Tuesday October 19, 2021 @05:53AM
(#28916471)
STEP files are like compiled binaries. Fine for distribution if you don't want to make changes to the file. But for a parametric CAD package like Solidworks or Onshape, much more information is saved. A parametric CAD file stores each step done to the part in order. This allows you to go back in time, change one feature, and re-apply the subsequent changes to the updated file. That's like source code to the part.
Re:Code CAD – Use code to create CAD models
by dotancohen on Tuesday October 19, 2021 @02:16AM
(#28915332)
Can STEP files be parsed to order via e.g. (I know nothing about them) sorting some tree? Are there any e.g. hashes that change as content is modified?
In software we solved this with code style guides and later code formatting tools. I would be surprised if e.g. a Python script could not format the STEP files to a "canonical" representation before committing the file to version control.
Re:Code CAD – Use code to create CAD models
by rjsw on Tuesday October 19, 2021 @08:27AM
(#28917342)
I don't think there is an easy way to process a file to make it conform to a certain style, take a look at an example [1] if you want.
[1] https://files.pine64.org/doc/datasheet/pinephone/PinePhone%2...
What I desparately want though is an on-disk format that's plaintext, makes sense, and results in reasonable diffs so that I can use git for version control.
I just don't understand, being familiar with git, how people can work with 'save and mark new version' style 'version control' that's so prevalent among tools that have anything at all.