@MatthewBlanchard and I had a good discussion about the scope of MFEKstroke.
Before layers were added to MFEKglif (layers dev branch), this project was used by MFEKglif to "flatten" the VWS out of a .glif file.
That's why VWS is weird here. It's the only one with no CLI API, and this strange description:
(Note: In VWS mode, it is expected that you are using MFEKglif to generate the input files. Therefore, not many helpful command line options are provided. If you wish to use VWS programatically, play with MFEKglif's VWS tool, get some output, and study it; then generate conformant XML.)
That's a clue that VWS is out of scope. It's too complicated to define a CLI API for, and MFEKstroke shouldn't be the one flattening it.
MFEKglif --export should be.
Therefore, I propose:
Removing variable_width_stroke.rs and the VWS mode;
Keeping VWS documented here, with its screenshot, but noting that it, like the other MFEKglif "flatten"/"export" operations, be done by MFEKglif --export.
That keeps the scope of MFEKstroke laser-focused: a CLI API for MFEKmath / path stroking in .glif files.
@MatthewBlanchard and I had a good discussion about the scope of MFEKstroke.
Before layers were added to MFEKglif (
layersdev branch), this project was used by MFEKglif to "flatten" the VWS out of a .glif file.That's why VWS is weird here. It's the only one with no CLI API, and this strange description:
That's a clue that VWS is out of scope. It's too complicated to define a CLI API for, and MFEKstroke shouldn't be the one flattening it.
MFEKglif --exportshould be.Therefore, I propose:
variable_width_stroke.rsand the VWS mode;MFEKglif --export.That keeps the scope of MFEKstroke laser-focused: a CLI API for MFEKmath / path stroking in .glif files.