Hi, I've finished the integration of the openSM2sync server and client in the desktop GUI. As usual, things that seemed easy at first turned out to be a lot less trivial than I originally thought :-) The sync server and the desktop app both need access to the same database, and I had to make sure they stayed out of each other's hair. Anyway, I had lots of fun and learned a lot about multithreading :-)
I've also added a section in the SM2sync docs with tips for sync client writers on how to make sure you get maximum performance. This basically completes the work on openSM2sync for 2.0. It took about a year, which contributions from many people, but it was definitely time well- spent, given the importance of mobile devices. I think we now have something that is quite unique in SRS land: a sync protocol which is fully bidirectional (adding cards on the desktop does not conflict with doing reps on your phone), can support multiple sync partners, and has a Python reference implementation which is optimised for speed and memory usage. Next, I'll deal with some non-sync related loose ends, and then it's the final big missing piece in the 2.0 puzzle: the card browser. Cheers, Peter -- 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 this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en.
