I'm pleased to announce the release of version 1.0 of TiddlyRemember, a tool to make it easy to remember the most important bits of your notes. You call out specific bits of your tiddlers that you want to remember using TiddlyWiki macros, and an associated Anki <https://apps.ankiweb.net> add-on then pulls these snippets into Anki where you can review them regularly. The Anki cards link back to the tiddler they came from so you can find the context if you need it, and if you edit the content in TiddlyWiki or move it around, your Anki collection gets updated to match on your next sync, maintaining your review history.
Here's a little snip of the syntax, the rendering in a TiddlyWiki, and the card in Anki (permalink to this page in the docs <https://sobjornstad.github.io/TiddlyRemember/#Question-and-answer notes>): [image: syntax.png] There are cloze deletion cards too (if you're not a memory geek, you might call these "fill in the blanks cards"). Credit for this idea goes to Andy Matuschak, who reported building a private tool that worked similarly for his notes system <https://notes.andymatuschak.org/>. I cannot for the life of me find this note now (if someone knows where it is, please post the link!). Check it out and install from here: https://sobjornstad.github.io/TiddlyRemember/. I'm hoping this is a reasonably stable and functional version (thus the 1.0.0 moniker), but I've only been using it myself for a couple of weeks as I've been developing, and there are definitely improvements possible, so suggestions and pull requests are welcome! The two biggest areas for improvement I see that I'm not sure how to attack are: - You have to have TiddlyWiki installed on Node on your system to use TiddlyRemember. (You can use TiddlyRemember fine with a single-file wiki though. It just has to be there for TiddlyRemember to call out to.) There's no way around this I can think if if you want a fully automated sync (the Anki add-on needs some way to run TiddlyWiki commands unless it wants to duplicate the wiki parser), but I could imagine a way to use the new browser-based static site generator tool as part of a two-step process where you export. - In order to extract the questions, TiddlyRemember renders all the tiddlers in your wiki and then parses the resulting HTML, which means it will end up pulling multiple copies of a question if the tiddler containing a question is transcluded into another tiddler that's included in the sync. It will happily remove duplicates, but there's no way for it to tell which tiddler is the "original source", so it picks whichever one it happens to process first, which isn't great. I don't tend to use transclusion much aside from adding templates to things and building up system tiddlers and sidebar tabs, so this isn't a big deal for me, but it might be for others. - I originally planned to make each question a tiddler of its own; while this seemed more philosophically pure, I eventually decided against this approach because I didn't like the idea of having to separately edit a bunch of subtiddlers for all of my notes, and because having the question included in a tiddler allows the source to be automatically determined without having to link back to it and update it if you move the question around (aside from the transclusion issue). But I could see an argument for doing it as transcluded question tiddlers, and maybe we could support that as an alternative method eventually (especially if it becomes easier to edit transcluded tiddlers in a future version of TiddlyWiki). -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/24a8066b-0c1a-42ad-9886-68421c4c2d5c%40googlegroups.com.
