On Sep 6 at 07:58 +0200, Peter Bienstman wrote: > BTW, from your recent mails I assume there are no concrete plans to > port this to Mnemosyne 2.0 and/or support openSM2sync?
The short answer is, sadly, that I currently have no concrete plans. For a longer answer... I'd definitely like to support the new version but the problem is finding bigger blocks of time! Each of the recent changes to Mnemogogo and clients was only a matter of two or three hours at most. As it stands, I consider versions 1.x of Mnemogogo/dodo/jojo finished, but I'll still release bug fixes and adjustments for various phones if necessary. For Mnemosyne 2.x and Mnemojojo, the best course of action may simply be to port the Mnemogogo plugin and leave Mnemojojo unchanged. There are three reasons: 1) To my mind, the best thing about Mnemojojo is that it usually works on relatively low-end (cheap) phones. Adding support for openSM2sync may be the final straw (or drop depending on where you come from). 2) Even though there are higher-end Java phones, I don't know much about the practicalities of a common database API, which would be necessary to reduce the implementation effort. 3) I've had enough of J2ME (both technicalities and politics). Mnemododo, however, should support openSM2sync: Android phones are more capable, the APIs are broader and more consistent, and the platform is easier to work with. Also, on these types of phones particularly, it's more natural to sync over a wireless network, and a pain to sync using a cable. I had sketched out a rough design for adapting the underlying library so that openSM2sync could be added with minimal changes to the GUI (which is now tested, and translated into several languages), but I haven't gotten any further than that. But I would be happy to help anyone who wants to add this functionality. Mnemododo is GPL2ed open-source software. And even though I currently charge for the build on the Android Market, this is not something I'm fanatical about. Tim.
signature.asc
Description: Digital signature
