Open colinmford opened 1 year ago
to keep a reference in the glyph lib is a good plan!
one issue I see is that this lib key is not something to keep in sync, its is just a reference where the components originally came from. If a designer adjust components manually, the construction will be out of sync.
I like the second option to keep the variable in the font.lib
In the extension this could be an optional flag: Store construction in lib.
Hm, good points, the "invalidating" of glyph construction glyphs that are then edited afterwards is giving me pause. I'm gonna give this more thought.
duplicated data on different levels of abstraction is a pain...
however to start over from stored glyph constructions is a deliberate decision, which can be shown in a warning dialog before appling
Hi @typemytype,
I have been thinking for some time it might be nice to have the equation to build a glyph constructed glyph saved in the glyph's lib, like so:
A few examples of what this would allow other scripts to potentially do:
*
)... And many more! (maybe)
The only hitch I can see is user-defined variables... I can see it working maybe 2 ways? Of course the Glyph Construction constants like
descender, xHeight
etc won't be touched, but we could expand the variables to put in the equation, or store the variable in the font lib.becomes
or
If you like this idea, I could make a PR.
Thanks!