| Age | Commit message (Collapse) | Author |
|---|
|
Include "Key" in the name because that's kind of the whole point.
|
|
Ready for initial public release.
|
|
Separate preference handling into a new class and have the previous
preferences class handle only the preferences window.
We rename the old file to `preferences_window.py` and adjust the
`info.plist` key for the menu item accordingly.
Our new `Preference` class can now be imported from both
`equalize_sidebearings.py` and `preferences_window.py` without causing
confusion. I extracted it because asking for the
`DEFAULT_ACTIVATION_KEY` from `preferences_window.py` from
`equalize_sidebearings.py` would open the preferences window (bad).
We now save the preferred key using RoboFont's extension preferences
API.
When the text input in the preferences window is modified, the new key
preference gets saved.
BUG:
There's an issue with this implementation where the preferred key
doesn't become active until the next launch of RoboFont because
`EqualizeSidebearings` has its own instance of `Preferences` which has a
stale `activation_key`.
|
|
* Add `info.plist` (apparently it needs to be lowercase, weird, who
knew?) that contains the necessary keys for the extension (as per
http://robodocs.readthedocs.org/roboFontDocumentation/content/extensions/specification.html#specificationextensions)
* Create a build script that copies the necessary files into the
extension's bundle folder
* Create a Makefile with some build and clean rules
|
