OpenJSCAD.org VS oce

its uses https://github.com/jscad/OpenJSCAD.org library to create the 3d model

then there are 2 others, sop/CSGboolean and sop/CADboolean. CSGBoolean is indeed based on CSG, and uses jscad. And the CAD one (which I show in the video in this post) is based on opencascade, which is the most powerful/stable. Then the output of both of those nodes is converted to threejs in order to be displayed in webgl.

That being said, https://github.com/jscad/OpenJSCAD.org sounds like a winner for your requirement of NOT having to download a file across the internet.

this looks very nice. i think i like the ergonomics of your library... the "sketch on a plane then extrude" workflow feels nice and familiar.

could you compare and contrast replicad to JSCAD (https://openjscad.xyz)?

the examples in your docs are quite sluggish to load in Safari, but the workbench is very snappy!

No one has mentioned OpenJSCAD, which is the same idea in Javascript: http://openjscad.azurewebsites.net/

https://github.com/jscad/OpenJSCAD.org/tree/V2

A fairly substantial rewrite is underway, the V2 branch linked above.

- Browserify to bundle the design into a website. Directly from the source CAD files, without rendering to a huge mesh file format.

It's cool because you get access to the whole javascript ecosystem, and it's native to the browser.

https://openjscad.xyz/

Have a look at https://github.com/tpaviot/oce/ Not sure if there is a go wrapper for it. There is a python library wrapping opencascade already.

Some parts of the 3MF are actually good. I like the spec documents winding order of the meshes. The format includes units, and these optional 4x4 transformation matrices — both are useful.

As for need of the new formats, for one, modern CAD formats are insanely complex. These IGES/STEP/BREP files require many megabytes of very complicated code to deal with, such as this library https://github.com/tpaviot/oce These formats may even contain proprietary extensions. Also, they need non-trivial processing power to handle. Many people wouldn’t want a Core i7 with gigabytes of RAM in their 3D printers, inflates hardware cost and software complexity.

Besides, we now have high-resolution 3D scanners, and CAE software which algorithmically optimizes models by running numerical simulations. They both output triangle meshes instead of CAD files. Scanners often output point clouds one can convert into triangles, but hard to convert into CAD formats.

I just don’t like the 3MF implementation too much. XML is fine for kilobytes of data, but not many megabytes. If I would be designing that format, I would probably made it binary. Maybe EBML https://en.wikipedia.org/wiki/Extensible_Binary_Meta_Languag... would work for that; it does fine for MKV videos, which is also a huge pile of structured data with non-trivial performance constraints for producers and especially parsers.

Another minor thing, it was not the best idea to make name start with a digit. Most programming languages forbid identifiers like that for their classes / functions / namespaces / modules.

Cadquery uses opencascade under the hood. I think your best bet is to open an issue and ask: https://github.com/tpaviot/oce