meolox wrote:

Too bad you can't review primitives on the site.

The SRS system for the actual kanji should ensure you review every primitive strictly at least as often as you would if it was its own separate flashcard, surely? The most extreme case would be if you had a primitive that only appeared in one kanji, and where you never failed that kanji for any reason other than failing that particular primitive. And in that case you'd see the card (and thus the primitive) on exactly the same schedule as if it was a card dedicated to the primitive. In practice, of course, each primitive appears in multiple kanji, so you see it more often than that, and you may well fail a card for other reasons than that primitive, which again makes it turn up more often.

So you already see each primitive on a much more frequent schedule than strict SRS of the primitive alone would require. Adding an extra card purely for the primitive would just make it turn up even more often. And we're trying to reduce effort here, not increase it, right? :-)

As is mentioned in the thread Transtic points out, you might want to share stories about the primitives, but you're not going to get that from Anki either...

Seeing that we work off a pre-designed Kanji database (this is true, right?), some of the primitives are already designed so no need to draw them. The only way I see that working (for now) is the list of the Heisig primitives that are in themselves Kanji also. This is the case for ones like Barracks and Moreover which Heisig points out in his book. I also believe the traditional radicals are in that database.

That leaves only the primitives that Heisig (and other users) just made up. For me, I can recall Birdnest (goods over tree).

Hmm, thinking on this a bit more, isn't in keeping with the RTK mindset to include ALL the kanji that make up the kanji you're actually learning? You find out in RTK3 that alot of the "primitives" are kanji in and of themselves. So definately those primitives should be added with the actual meaning used as the keyword.

The problem is including these primitives without messing up the Heisig number order (which seems to be an important order for a number of reasons). That being the case, RevTK could incorparate primitives in the study via a method that KanjiCan uses. In that program, he lists primitives with decimal points. So the "drop" would be 21.1 for example if it it shown right before frame 21. I'm guessing there's a way to then to use pre-existing primitives and insert them into the RevTK list. All one has to do is list the non-frame primitives with the database locator (easier said than done, I know).

That leaves only the primitives that Heisig invented. Eh.