AnkiWeb addon 1014777615
Generates graphical forms from JSON schemas to edit configurations of compatible add-ons, replacing manual JSON text editing for supported simple settings.
Open on AnkiWeb GitHub Find alternatives
abandoned
| Min Anki | Max Anki | Updated |
|---|---|---|
| 2.1.0 | 2.1.21 | 2020-03-12 |
| 2.1.22 | + | 2020-03-19 |
Loading…
Adds a dialog and context menu entries for inserting, editing, and unlinking hyperlinks in note fields, with configurable keyboard shortcuts.
Links Anki notes together via a custom link format, adding link panels, interactive graphs, and a global relationship graph.
Automatically bolds target Japanese vocabulary within sentence fields using morphology-aware matching, with dry-run preview, browser integration, custom readings, and optional furigana clearing.
Colors deck names in the browser via a graphical interface with color pickers, live preview, and apply/remove controls.
Imports chess PGN game collections into Anki decks, creating opening-repertoire flashcards with board diagrams, annotations, and nested variations, while allowing re-imports without losing learning progress.
Automatically generates Japanese-to-Japanese definitions from bolded source-field words via the goo.ne dictionary, filling empty destination fields across add, browse, and edit windows.
It only works with add-on which were made compatible with the current add-on; which is really easy to do. 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 |