Hacker News new | ask | show | jobs
by fsloth 71 days ago
Theoretically, yes, but in practice a structured XML description of a parametric model is not useful in the general case without standardized format.

STEP XML would be probably the closest here.

To be realistic, I might wrap a CLI to AdaShape first, then the user could query the model and have their LLM backport the model tree to something like CadQuery :D
1 comments
WillAdams 71 days ago
I am fine with a representational XML which depicts the contents of the tree with the data for each node --- my idea is I would parse the XML and re-create the structure inside my program (which is pretty much what I had in mind for supporting BlockSCAD).
link
fsloth 71 days ago
Ah, ok, so do I understand correctly you would sort of like a visual preprocessor for programmatic model data?

And specifically ”whatever xml”, not, say STEP, or , openscad code, python code (via using cadquery) or anything like that?

Do you know your final output format?

link
WillAdams 71 days ago
I would like a way to take a 3D model which has been made in an interactive tool such as your tool or BlockSCAD, then export the descriptive representation (so the 2D and 3D geometry and parameters and instructions for interaction) as an XML file (BlockSCAD does this as its "native" format, allowing one to save a design locally and reload it.

Then, I would import that into my project, parse the geometry and instructions for processing it so as to create a 3D model, then I would work through the toolpaths necessary to cut the part thus described using G-code. Or, at least, that's what I would like to try to do. I'll have to give it a whirl w/ BlockSCAD if nothing else.

link
fsloth 70 days ago
Export of the parametric model would fit well with the user respecting philosophy underpinning the whole project.

While https://xkcd.com/927/ is something to be avoided there really isn’t an existing format I would be aware off that fits the bill.

I’ll add this to the roadmap.

But to do this right it really needs to be a properly specified schema, with conformance test suite and versioning.

I appreciate your use case, but for users coming out of context, parsing underspecified XML files would be more of a curse than blessing :)

link