Wow! This is great news. Will it be free or paid? If free, will it be
open sourced? Either way, it would be good to have Mnemosyne on the
iphone/ipod.
Robert
Nice! To add some more questions, is it based on the 1.x or the 2.x codebase?
Is it a native client or is it for jailbroken devices?
Peter
If it is going to be a closed, proprietary application, I *strongly*
urge you not to call it iMnemosyne or anything with 'Mnemosyne' in it.
Peter may not've actually filed a trademark on Mnemosyne, but the
moral point is still there.
--
gwern
> Having said that, iMnemosyne is an independent project written from
> scratch :).
I have some questions about the development of iMnemosyne.
When I read the name of your app "iMnemosyne" and how
you said you are implementing the look and feel of the current
version on the iPhone, I assumed you were porting the code base
of Mnemosyne to the iPhone.
Now you are claiming you have developed the program from
"scratch", yet you have appropriated the product name,
and you are copying the look and feel.
Unless you are providing a free port of Mnemosyne for the iPhone
that works the same as the Windows and Linux version of the product,
then I don't think it is right you are copying the name and look and feel.
This is downright confusing.
I tried to find the licence under which the Mnemosyne source code is
released but it is not stated on the web site.
(http://www.mnemosyne-proj.org/hacking.php)
but maybe the source code contains this?
Please tell us more about your product and how your development fits
in with Mnemosyne.
It does; the repo, for example, has a copy of the GPL at
mnemosyne/LICENSE. Your distro packages like Debian's package will
generally tuck that away somewhere.
--
gwern
> Now you are claiming you have developed the program from
> "scratch", yet you have appropriated the product name,
> and you are copying the look and feel.
Imitation is the sincerest form of flattery :-)
I have no problem with charging for an application, as I can understand the
argument of wanting to recover your development fee.
However, if you are going for a closed-source paid-for app, then it's perhaps
better to pick a different name, as you already suggested yourself.
If on the other hand you go for an open-source paid-for app (yes, that's a
valid legal combination!), that would put me in a position to review your
code, and iMnemosyne could then perhaps even become the "official" Mnemosyne
client for the iPhone (even though one could have to pay you for the
convenience of downloading a binary from the Apple store). Obviously, another
iPhone developer could at a later stage decide to take your code and
distribute it for free on the Apple store.
Regardless of which route you go, I'm very much in favour of interoperability
with the desktop version of Mnemosyne. That's what libSM2sync is all about:
http://bazaar.launchpad.net/~peter-bienstman/mnemosyne-
proj/trunk/files/head%3A/mnemosyne/libSM2sync/
(it does require you to hang on to the revision history for syncing and log
upload, though.)
So, in summary, I'm very supportive of your project. A native iPhone companion
app to Mnemosyne will surely be very useful for many Mnemosyne users,
regardless of its name, price or license.
Good luck!
Peter
I would love to make one. I just never seem to get around to it though :).
Robert
If you want people to move all their data back and forth between the ipod and
the desktop, I suggest that you also collect the history that gets dumped into
log.txt. If you don't, the statistics graphs in Mnemosyne 2.0 will become
skewed and that might be a hurdle for people to use your software.
Cheers,
Peter
If possible, I think it would be best to set up some way to
synchronize it automatically. So you would set it up with the location
of your server and then it could synchronize that file. Of course you
could always launch a website to provide hosting and such for people's
flash cards.
Jason
The log.txt for uploading to the central server is the same, but 2.0 that data
is actually stored as well in the sqlite database, just like the card data. I
don't think 2.0 will have a native xml import/export format anymore, the
recommended way for getting data into and out of Mnemosyne from other SRS
programs is through openSM2sync.
Although there is a high level description of openSM2sync, there is no
complete implementation yet. Max is working on one in Python in the context of
the Maemo client, but as far as I know, it's not finished yet and is not merged
into the trunk.
Peter
Peter,
This makes it sound like it will be harder to make backups of
flashcards. Or perhaps the files will now simply be in a openSM2sync
file format rather than XML?
Jason
The automated backups now just make a copy of the sqlite database. For the
manual backups, you can do the same.
The sqlite format is well-known, open and publicly documented, so I don't
think it makes sense to spend effort on a separate XML schema to store all the
data. (There is much more data in the database now than in 1.x)
Cheers,
Peter
> Hello, Peter!
> I have finished implementing openSM2sync protocol and it works fine! But
> I still haven't write tests for this module because of my illness.
> During next week I am going to do it.
Wonderful! Get well soon!
Peter