On Nov 29, 9:09 am, Zak Gottlieb <[email protected]> wrote: >But anyway, it adds too much complication, > whereas it seems Mnemosyne neatly compartmentalizes this into plugins.
I like Anki's templating feature which abstracts data from card layout. But, the new v2 seems too esoteric for my tastes. For the example, the browser is like a super browser of all decks, tags, etc. A lot of noise when all I want to do is browse the current deck. It's just a way of approaching things which, to me, doesn't feel intuitive. I go into the browser and it doesn't default to browsing the deck I'm viewing. And, it has a zillion tags that aren't related to the deck I'm viewing. It's gonzo powerful... but I just want to browse the deck I'm viewing, not the universe. I get the same feeling about the distinction between "learning" and "review" modes. To me, this seems like an arbitrary way of dispensing of sub-day scheduling. If the interval could be in sub-day units, then "reviewing" would be one *continuum* from new cards which need to be reviewed more frequently (scheduled in 10 minutes, 20, 60, 200) and finally growing beyond the day-sized boundary (1440). Losing sub-day granularity has apparently had an unintended consequence. Cards are constantly displayed in order added because there is no sub-day ordering to maintain some randomness. I don't think plugins are a panacea however. That can turn into nightmare of dependencies, and time spent experimenting with plugins. For example, I can't imagine a use case where templating wouldn't be useful. So, implementing it as a plugin seems needless burdening of the introduction process, discovering and installing what is essentially a universal plugin. -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
