AnkiWeb
- Rating
- 4 (π 4 Β· π 0)
- Updated
- 2020-03-19
- Anki versions
- 2.1.22~
- Description language
- en
AnkiWeb addon 1014777615
Generates graphical forms for editing compatible add-on configurations using JSON schemas, supporting simple schemas while JSON text editing remains available.
Open on AnkiWeb GitHub Ask about alternatives
abandoned
| Min Anki | Max Anki | Updated |
|---|---|---|
| 2.1.0 | 2.1.21 | 2020-03-12 |
| 2.1.22 | + | 2020-03-19 |
Loadingβ¦
Adds hyperlinks to note fields through a dialog and context menu, with configurable insert and unlink shortcuts.
Connects Anki notes via [Title|nidID] links, with editor tools, link/graph panels, global relationship graph, and mobile rendering fallback.
Colors Anki deck names in the browser through a graphical interface with dropdown selection, color pickers, live preview, apply/remove controls, and JSON configuration.
Automatically bolds target vocabulary in Anki sentence fields using morphology-aware matching, with deck/note targeting, preview, browser integration, custom readings, and optional whitespace stripping.
Creates Anki decks from PGN chess games to train opening repertoires for White or Black, preserving progress, with board diagrams, variations, annotations, and Lichess links.
Automatically generates Japanese-to-Japanese definitions for bold words in a source field via goo.ne, filling an empty destination field and supporting configurable card types.
Currently, anki's add-on are configured using a simple json text. This is not practical for people not used to deal with programming and text format.
I thus wanted to create forms for my add-ons. And was too lazy to create a form for my 60 add-ons and for the add-ons I use. So instead I created a form generator.
This form generator still need a little bit of work for each add-ons. It needs the add-on creator to gives a json schema. I believe however that adding a schema is easier than creating a form. At least because add-ing a schema will be useful even if you don't care about the current add-on since anki 2.1.22 will use them to validate user's configuration before saving them.


This add-on can currently only deal with simple schemas. That is, lists, objects (dictionnaries) in which all parameters are known, file path, directory path, string, integers, floating point number...
This should change as the add-on evolve. There is no reason to worry however, because if the add-on does not work, you can still use normal configuration editor.
Add-on schema only let you tell that the expected type of a value, e.g. a string. In order to let Anki know which kind of user interface should be displayed to let the user enter the value, you nay add a parameter "ui:widget". E.g. "ui:widget":"colour" indicates that the string should be selected using QT's color selector. Please see documentation to see all options.
This add-on uses qt-jsonschema-form as a submodule. Once you have downloaded the current add-on, you should do git submodule init to download the submodule and ensure that you are on the branch ui_in_schema.
Dealing with extra parameters. Dealing with values which may have multiple types (or even none type)
| Key | Value |
|---|---|
| Copyright | Arthur Milchior arthur@milchior.fr |
| Based on | Anki code by Damien Elmes anki@ichi2.net |
| License | GNU AGPL, version 3 or later; http://www.gnu.org/licenses/agpl.html |
| Source in | https://github.com/Arthur-Milchior/anki-gui-for-addon-config |
| Addon number | 1014777615 |