-
Notifications
You must be signed in to change notification settings - Fork 475
[varLib] Use designspaceDocument? #911
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
Comments
+1 for using designspaceDocument, +2 for including it in fonttools if Erik steps up to maintain it |
Are the dependencies really hellish? It seems to be smooth to me. Curious
what the advantages of inlining it are? 🤔
…On Apr 8, 2017 10:07 PM, "Cosimo Lupo" ***@***.***> wrote:
+1 for using designspaceDocument, +2 for including it in fonttools if Erik
steps up to maintain it
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#911 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAP9yxp7F5nB-gBG16NmHsT4OD3lewA2ks5rt-kegaJpZM4M3zHt>
.
|
Yes, they are. |
If this is the way to go, I don't mind maintaining it. |
Thanks Erik! You already have push access, so you can create a new branch here on the fonttools repo where we work together on integrating the new subpackage into the library. |
Maybe outside of varLib, as fontTools.designspaceDocument, would be better. |
I like folding it in as well. Will review the code / api. |
Already done #1313. |
Should
fontTools.varLib
use @LettError’s designspaceDocument class?Thoughts? Perhaps designspaceDocument coud become part of fonttools?
The text was updated successfully, but these errors were encountered: