|
From: | Urs Liska |
Subject: | Re: Other programming languages & LilyPond |
Date: | Tue, 03 Dec 2013 11:22:07 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 |
Am 03.12.2013 11:12, schrieb Henning Hraban Ramm:
Thanks for that explanation. So Anki decks aren't really accessible to version control, i.e. a Git repository. AFAICS in order to maintain a deck collaboratively one would need a server application that interacts with the SQLite dbs. Which is of course feasible (I think SQLite support is nearly anywhere), but would of course need considerable more effort than simply initializing a repo.Am 2013-12-03 um 14:42 schrieb Urs Liska <address@hidden>:Am 03.12.2013 09:35, schrieb Curt:Collaboratively creating lilypond anki decks could be clunky. You'd probably be collaboratively editing the generating scripts themselves, and then be building the decks from that, and then reimporting on top of your already existing deck, which could be problematic.Hmmm. In which form are decks and cards stored on disk with Anki?A small file tree with several SQLite dbs: Anki ├── Hraban │ ├── backups │ │ ├── backup-13.apkg │ │ ├── backup-14.apkg │ │ ├── backup-15.apkg │ │ └── backup-42.apkg │ ├── collection.anki2 │ ├── collection.log │ ├── collection.media │ ├── collection.media.db │ └── deleted.txt ├── README.txt ├── addons └── prefs.db
OTOH I could imagine there already exist working approaches. No time to research, though :-( Urs
[Prev in Thread] | Current Thread | [Next in Thread] |