Anki is a smart spaced repetition flashcard program
Find a file
Damien Elmes b5c0b1f2c7 drop required/unique field properties
Instead of having required and unique flags for every field, enforce both
requirements on the first field, and neither on the rest. This mirrors the
subject/body format people are used to in note-taking apps. The subject
defines the object being learnt, and the remaining fields represent properties
of that object.

In the past, duplicate checking served two purposes: it quickly notified the
user that they're entering the same fact twice, and it notified the user if
they'd accidentally mistyped a secondary field. The former behaviour is
important for avoiding wasted effort, and so it should be done in real time.
The latter behaviour is not essential however - a typo is not wasted effort,
and it could be fixed in a periodic 'find duplicates' function. Given that
some users ended up with sluggish decks due to the overhead a large number of
facts * a large number of unique fields caused, this seems like a change for
the better.

This also means Anki will let you add notes as long as as the first field has
been filled out. Again, this is not a big deal: Anki is still checking to make
sure one or more cards will be generated, and the user can easily add any
missing fields later.

As a bonus, this change simplifies field configuration somewhat. As the card
layout and field dialogs are a popular point of confusion, the more they can
be simplified, the better.
2011-11-24 22:16:03 +09:00
anki drop required/unique field properties 2011-11-24 22:16:03 +09:00
tests drop required/unique field properties 2011-11-24 22:16:03 +09:00
tools apply review limit; fix finished msg 2011-11-15 04:05:44 +09:00
.gitignore add coverage testing 2011-11-08 20:29:47 +09:00
ChangeLog.old initial commit from hg 2008-09-27 23:50:03 +09:00
LICENSE update license link 2011-04-28 09:24:01 +09:00