Damien Elmes de8a5b69ed top level groups ... As discussed on the forums, moving to a single collection requires moving some deck-level configuration into groups so users can have different settings like new cards/day for each top level item. Also: - store id in groups - add mod time to gconf updates - move the limiting code that's not specific to scheduling into groups.py - store the current model id per top level group		2011-09-07 01:31:46 +09:00
..
off	some initial sync work	2011-05-29 08:13:54 +09:00
support	ensure duplicate model creation times are accounted for	2011-08-26 22:33:24 +09:00
__init__.py	initial commit from hg	2008-09-27 23:50:03 +09:00
shared.py	drop sqlalchemy; massive refactor	2011-04-28 09:23:53 +09:00
test_cards.py	top level groups	2011-09-07 01:31:46 +09:00
test_deck.py	top level groups	2011-09-07 01:31:46 +09:00
test_find.py	move tags into deck; code into separate file	2011-08-28 13:44:29 +09:00
test_latex.py	move models into the deck table	2011-08-27 22:27:09 +09:00
test_media.py	rename()	2011-04-28 09:24:05 +09:00
test_models.py	top level groups	2011-09-07 01:31:46 +09:00
test_sched.py	top level groups	2011-09-07 01:31:46 +09:00
test_stats.py	move models into the deck table	2011-08-27 22:27:09 +09:00
test_sync.py	move models into the deck table	2011-08-27 22:27:09 +09:00
test_undo.py	top level groups	2011-09-07 01:31:46 +09:00