Catherine

@tetsuharu That's not really feasible because the SLVS format can represent infinitely many times less geometry than the STEP format; STEP allows arbitrary NURBS geometry and far more, SLVS only...

Unfortunately this won't work, as there is no way to construct an arbitrary bounded solid right now. You should not convert STL to entities (which is very inefficient anyway), but...

That would be a good tool, but as far as I know it's an extremely complex project to tackle if you want to get good results.

@jwesthues Any objections? Disregard my earlier thoughts about using LLVM bitcode; after an in-depth discussion with LLVM folks that turned out to be a rather poor choice.

The new file format should also use 64-bit handles (as would the in-memory representation). The rationale is that, once we make large assemblies fast, remapping of entities can rapidly exhaust...

Actually, the version 3 of Protocol Buffers has a canonical JSON serialization, so we could just use that. (Google generally recommends version 2, for reasons that I do not fully...

It's also worth taking a look at [Cap'n Proto](https://capnproto.org/), designed by the original author of Protocol Buffers while taking into account many of the downsides of the latter. It has...

@Evil-Spirit > Actually when I implementing dxf import, I've easily found file which doesn't fit into 64k handles. I don't consider importing such files useful (what are you going to...

@jwesthues Can you please write a (more in-depth than the comment in sketch.h) explanation of the function that remapping serves? I see that it's used for both assemblies and any...

Speaking of Protocol Buffers... I'm looking further into it and I see some potential scalability problems. Specifically, Protocol Buffers are designed to work by deserializing the entire message at once....