Consider support for multiple instance writes during a single execution
chrissimpkins opened this issue · comments
e.g., full RIBBI family
@rsheeter suggested that with the ability to define a set of instance location and write them out as a single run, users will want to save and reuse a slice config, say for the next build of the font.
Also in defining a set of instance locations, the ability to slice a subspace (#17) as well as a set of static instances would be good.
@rsheeter suggested that with the ability to define a set of instance location and write them out as a single run, users will want to save and reuse a slice config, say for the next build of the font.
I really like this idea. Thoughts about how a user would want to approach the configuration?
slide a subspace
What do you mean by "slide a subspace"?
What do you mean by "slide a subspace"?
Typo! "Slice a subspace." :) Subspace is my preferred term for partial instance, since that phrase centers instances but I think spaces should be centered. There isn't a right answer; its a glass half full/empty distinction.
how a user would want to approach the configuration?
I guess a slice.yaml (or toml, or json, or whatever) file that just has the (nested) dicts of metadata the app consumes.