On Thursday 14 May 2009 09:55:28 am Robert Gravina wrote: > Are you talking about the Python application itself, or the algorithm?
Both. > If someone was to develop an iPhone app, it would make sense to make > it a native app (unless Apple decides to allow Python etc. on the > iPhone). Definitely. > If you're just talking about the python application, then I suppose > the iPod app could be more or less a clean-room implementation, > although using the same algorithm and data files/formats... Yes. 2.0 uses a sqlite database, which is much better than the format in 1.x where everything is kept in memory. In any case, even if you implement it in a different language, it's best to look at the 2.0 codebase for inspiration. E.g., the scheduler has roughly similar behaviour in both codebases, but the implementation is rather different, and more optimised in 2.0. > In either case, if I was to think about working on an iPhone native > app, I'd take a look and see what's being done in 2.x first. I think > that the iPhone app would still be useful with a limited set of > features - review + sync only at first, Absolutely. That's the same path I'm taking for the WM client. 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 -~----------~----~----~----~------~----~------~--~---
