I've been thinking of making a tool that will output g-code based on similar ideas to what you have here, however, I think I would try to work directly in go or python instead of expressing the shapes as json.
Making thinking was something like:
pros:
1. json has lots of tooling and is generally easy to work with 2. if I put up a ui/webapp around hfd, then json will work well for that. 3. if I want a custom DSL, I can always have the grammar convert to json as the underlying representation.
CONS: 1. the json ends up being deeply nested and hard to work with 2. lack of multiline strings and comments (I went ahead added comment support though :))
We have a platform for automated sheet metal production and quoting. At the moment we only take completed 2D/3D technical drawings as an input although there is definitely a market for ordering parametric products too.
If you ever want to discuss the possibilities for HFD in the sheet metal industry let me know!
HFD is meant to make it easier to create designs which are parameterized (i.e. one design where you could easily change the width, height, thickness, ect). And make it simpler to split and layout designs across multiple pieces of material.
so sorta like OpenSCAD (the language, not the program), but specialized for 2d/planar work?
