737a8d934e
- add-ons can ship default config in a config.json file
- users can edit the config in the add-ons dialog, easily syntax-check
the json, and restore it to the defaults
- an optional config.md contains instructions to the user in markdown
format
- config will be preserved when add-on is updated, instead of being
overwritten as is the case when users are required to edit the source
files
A simple example: in config.json:
{"myvar": 5}
In your add-on's code:
from aqt import mw
config = mw.addonManager.getConfig(__name__)
print("var is", config['myvar'])
Add-ons that manage options in their own GUI can have that GUI
displayed when the config button is clicked:
mw.addonManager.setConfigAction(__name__, myOptionsFunc)
|
||
|---|---|---|
| anki | ||
| aqt | ||
| designer | ||
| tests | ||
| tools | ||
| web | ||
| .gitignore | ||
| .travis.yml | ||
| anki.1 | ||
| anki.desktop | ||
| anki.png | ||
| anki.xml | ||
| anki.xpm | ||
| LICENSE | ||
| LICENSE.logo | ||
| Makefile | ||
| README.contributing | ||
| README.development | ||
| README.md | ||
| requirements.txt | ||
| runanki | ||
Anki
This is the development branch of Anki.
For stable builds, please see https://apps.ankiweb.net.
For non-developers who want to try this development code, the easiest way is to use a binary package - please see https://anki.tenderapp.com/discussions/beta-testing
To run from source, please see README.development.
