bisen2 / fsscad Goto Github PK

The sample currently only uses a small subset of the API, it would be good to expand it to demonstrate other parts of the library.

Currently, the API exposes a DU listing all of the valid color names. There are a few reasons that this may be a potential problem:

• Any changes to this DU would be a breaking change
• This will be a bit of a pain to maintain. How often do these values change? Is it worthwhile to come up with a more automated solution to keep this current?

There are a lot of helper functions that should be added to the ComponentBuilders module. Some examples:

• Functions defining curried factories for all base component types
• Functions utilizing default values for each base component or transformation
• Partially applied variations of transformations (translateX, translateY, etc)
• Functions for defining combinations of components (perhaps using computation expressions?)

For both ColorHex and ColorName , the current signatures are color:string * target:Component -> Component. In both of these cases, not all strings are valid inputs for the color argument, so we should introduce types to better define the valid inputs. In particular:

• ColorHex's color argument should take a type that allows only valid color hex codes
• ColorName's color argument should take a DU that defines all of the valid color names

Right now the generated OpenSCAD is not at all formatted - it all outputs as a single line. It would be nice if we could insert some newlines and indents to make the generated code easier for a human to read.