-
Notifications
You must be signed in to change notification settings - Fork 9
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
avar3: Multi layered virtual masters #161
Comments
Is this about:
? |
We should first rule out that this is not just a compiler distilling to avar2. I'll think about that. |
Here is a simple example of "multi-layer avar" (hmm, how many layers is this? fences or fenceposts?), using subscript digits to indicate the axis layer number:
xxUC, xxLC, xxFI mean uppercase, lowercase, figures respectively. (I prefer the 'control' metaphor to the 'blend' metaphor, since that’s the direction inputs turn into outputs when the font is in use.) During the avar2 design process, @behdad wondered if to allow more than 1 mapping layer. I confess I resisted it because of complexity, and I don’t think a spec concept emerged. However I think if we allow axisIndexMap to contain n * axisCount records, where n is the number of layers, we’re good :) Discussing with @behdad. |
The number of entries in |
I'm convinced myself that distilling it to avar2 will explode the number of tents. So, I'm happy to work on a avar3 to address that. It looks like we just need to add a |
SGTM |
How is a high number of tents an actual problem? |
Okay I confess, I haven't actually figured out how to work out the conversion. If we know how to merge two layers, then the rest follows. What I had in mind was roughly that, for each linear piece of the piece-wise-linear mapping from the first layer, we need to insert all the segments from the second layer that are in range. I'll think more about it, see if I can actually prototype. But with multi dimensions it becomes really crazy to wrap one's head around. |
I worry about this. avar2 is already quite complex, and hard to explain to designers. To add another dimension (hah!) of complexity should not be a light decision. |
Perhaps that is where the 'blending' metaphor is useful, then. If you have a paint palette and you blend 2 primary colors you get a secondary color. With two secondary colors blended, you get a tertiary color. There are many common ways to visualize this kind of simple tree structure, like the "mind maps" of any business class and "playoff" maps of any sports tournament :) |
It is useful to be able to develop 'atomic' parametric axes (like XOPQ, XTRA) and then mid level 'molecule' virtual axes (that combine them in specific proportions) that are then used to blend top level 'user' axes (weight, width, opsz).
I request this based on discussions with @dberlow and @Lorp
The text was updated successfully, but these errors were encountered: