|
1 | | -## Interpolation Matrix (MutatorMath) |
2 | | -================ |
| 1 | +Interpolation Matrix (MutatorMath) |
| 2 | +================================== |
3 | 3 |
|
4 | | -_This version of Interpolation Matrix is based on a fork of the original version by Loic Sander._ |
| 4 | +_This version of Interpolation Matrix is a fork of the original version by Loïc Sander._ |
5 | 5 |
|
6 | | -The interpolation matrix is a tool requiring at least two master fonts open in Robofont and interpolable glyphs, if the glyphs are incompatible, no instance will show. It allows you to preview interpolation and extrapolation based on master position in an grid. |
| 6 | +The interpolation matrix is a tool requiring at least two master fonts open in RoboFont and interpolable glyphs (if the glyphs are incompatible, no instance will show). It allows you to preview interpolation and extrapolation based on master position in a grid. |
7 | 7 |
|
8 | | -This version of the script (suffix -mutatormath) & the extension are a rewriting of the previous Interpolation Preview Matrix (see below) now using  <3, whereas previous inter/extrapolations where written by my simple self. |
| 8 | +This version of the script & the extension are a rewriting of the previous Interpolation Preview Matrix, now using LettError’s [MutatorMath](http://github.com/LettError/MutatorMath) ❤️ whereas previous inter/extrapolations were written by my simple self. |
9 | 9 |
|
10 | | - |
| 10 | +☞ [check out the demo on Vimeo](http://vimeo.com/109734720) |
11 | 11 |
|
12 | | -The glyphs are updated (almost) at draw time [mouseUp, keyUp], so you can modify glyphs and see changes happen in the matrix. Theoretically, you can have a 15x15 matrix of 225 fonts, beyond, it would get too slow to use… Testing indicates that 7x7 is the ‘maximal-optimum’ use case. |
| 12 | +### Previewing interpolations |
13 | 13 |
|
14 | | - |
15 | | - |
| 14 | + |
16 | 15 |
|
17 | | -You can use the matrix to generate font instances or compatibility check reports. You choose which instance(s) to generate by naming their ‘coordinates’ (A1, B4, C3, etc.), or you can generate instances by whole rows/columns (A, 1, etc.), or all at once (*). Generated instances are issued in a folder next to the source master font (which you indicate before generating). |
| 16 | +The glyphs are updated (almost) at draw time [mouseUp, keyUp], so you can modify glyphs and see changes happen in the matrix. Theoretically, you can have a 15×15 matrix of 225 fonts; beyond that, it would get too slow to use… Testing indicates that 7×7 is the ‘maximal-optimum’ use case. |
| 17 | + |
| 18 | +### Generating instances |
| 19 | + |
| 20 | + |
| 21 | + |
| 22 | + |
| 23 | +You can use the matrix to generate font instances or compatibility check reports. You choose which instance(s) to generate by naming their ‘coordinates’ (A1, B4, C3, etc.), or you can generate instances by whole rows/columns (A, 1, etc.), or all at once. Generated instances are issued in a folder next to the source master font (which you indicate before generating). |
| 24 | + |
| 25 | +### Saving matrices |
18 | 26 |
|
19 | 27 | Last but not least, you can save matrices: grid size, window size and master fonts are stored and can be reaccessed quickly. The matrix stores a simple .txt file. It’s not ideal but does the trick for now. |
20 | 28 |
|
21 | | -Demo on Vimeo: |
22 | | -http://vimeo.com/109734720 |
|
0 commit comments