On Sep 6 at 10:04 +0200, Peter Bienstman wrote: > > Mnemododo, however, should support openSM2sync: > > Apart from porting Mnemododo to Mnemosyne 2.0, there is actually > another route. Just run the Python libmnemosyne 2.0 codebase on > Android, together with the webserver for reviews over http (did I > mention already that I'm working on this, and that this is almost > finished?). Point the Android browser to the correct local port, and > you're good to go. Syncing can initially happen by running a > separate Python script.
That sounds like a very nice idea. > This has the huge advantage that all the existing 2.0 code can be > reused. This would be a huge advantage. > For a future, more streamlined user experience, there could be a > very simple app (either in Java or Python) which combines these > elements, adds a fancier css specifically tailored for Android, > etc.. Maybe this is the way forward (particularly since, in any case, I can't commit to making the necessary changes to Mnemododo). Still, people can still make use of Mnemododo until Mnemosyne 2.x and the new client are ready. Tim.
signature.asc
Description: Digital signature
