forked from MatthewBlanchard/MFEKStroke
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scope #14
Labels
meta
An issue of scope, goals, maintainership, etc
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@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:
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:
variable_width_stroke.rs
and the VWS mode;MFEKglif --export
.That keeps the scope of MFEKstroke laser-focused: a CLI API for MFEKmath / path stroking in .glif files.
The text was updated successfully, but these errors were encountered: