b78480fe52
This commit solves a problem that I had many time in the past. When I create a new model, I usually want to edit it. Clone of existing models present no interest by themselves. And as soon as I edit it, I need to do a full sync. As far as I understand ankiweb (which is sadly closed source), the full sync is required because ankiweb needs to know that the model associated to note type on the server did change. But since the model is new, it has no note type associated to on the server, so there is no need to do a full sync immediatly. Since the model is new, it also means there is no risk of the inconsistency with a change made in another computer/smartphone. Thus, when a field/template is added, I check that the model is not new by checking both whether it's id is not null, and also that it's usn is not -1. (I set usn early in the model's life) If it does not make into anki, then it'll be an add-on. But it's worth a try first. |
||
|---|---|---|
| anki | ||
| aqt | ||
| designer | ||
| tests | ||
| tools | ||
| web | ||
| .gitignore | ||
| .pylintrc | ||
| .travis.sh | ||
| .travis.yml | ||
| anki.1 | ||
| anki.desktop | ||
| anki.png | ||
| anki.xml | ||
| anki.xpm | ||
| LICENSE | ||
| LICENSE.logo | ||
| Makefile | ||
| pkgkey.asc | ||
| 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.
If you are interested in contributing changes to Anki, please see README.contributing before you begin work.
