cangy wrote:
just installed debian using this method:
...
so, almost usable now, with any luck it should be fine with a few tweaks and the new back end!
Hi cangy,
I've gone down a different path. After I gave up on Angstrom, I decided to see if the Zaurus was capable of the underlying Anki library (libanki) without any changes. It turns out that it actually can. You have to do a small witch dance to get Python and other dependencies to work with the Sharp ROM, but it's quite easy.
All that remains now is to write a decent GUI that will work with the Sharp ROM. Anki uses QT4, which is way ahead of what's part of Qtopia on the Zaurus (seems to be QT/Embedded 2), so the GUI needs to be pretty much rewritten.
The good news is that it really isn't that hard to write a simple GUI with basic features to cover a substantial amount of Anki functionality. I've spent a bit of time this weekend on this, and so far I have a GUI that allows you to load a deck, review cards, and save your progress. I've run into the same speed issues that you mentioned, but was able to work around some of them in my code. Most importantly, fetching a new card and reviewing takes less than a second. This makes it borderline usable as a stand-alone review tool. Saving a deck takes a couple of seconds though, as you've mentioned.
I started to play with syncing but haven't been able to get it to work completely. The Zaurus has very limited memory resources and that's preventing syncing from working fully.
It sounds like resolve has planned to address the speed and memory issues in a future release of Anki.
If anyone would like to play around with the Anki port to QT/Embedded or Qtopia, then please drop me a line. It's an alpha at the moment but extra testing is always good 
Cheers,
Misha