This is good news. I can't wait for the speed improvements and other misc. stuff. I'm sure it's going to go from really good (now) to even better! I wish I could help in the programming department, but I just don't have the ability nor the time. All I can say is, "Thank you for your efforts."
Request: Is it possible to change the formatting on a per deck basis? I see that having separate fonts for the question and answers are in the works, which is great. However, so of my decks, I would really like to have align left for them, while the others are just fine with the centre alignment. Is this functionality possible or in the works? In addition, taking out some of the need to edit the config.py file and putting the options in the UI would be beneficial in my opinion. On May 24, 6:11 pm, Peter Bienstman <[email protected]> wrote: > Hi, > > I've just moved a big chunk of work from my pbienst branch on Launchpad to the > trunk there. > > The most important user visible changes are: > > * scheduler improvements: less chance of seeing the same card two times right > after each other, failed cards in 'learning ahead' will now be shown again > during 'learning ahead' > * a plugin for a cramming scheduler which goes through your cards in random > order and does not affect the normal scheduler data. It is visually > distinguished from the regular scheduler by having only two grade buttons > (Right and Wrong) > * more flexible and faster startup scheme > * improvements in the Windows Mobile client > * reworked the library design so that during review, the library has to do 10 > to 20 times less work. The result is that on my WM phone, review time is now > completely dominated by the GUI toolkit, so things look good. > * multiple people can now use a single instance of the library at the same > time. Useful if somebody wants to implement a high-performance web server on > top of Mnemosyne > > One could argue that many of these features are not essential for a 2.0 > release. That is true, but implementing them has brought to light many > weaknesses in the library design, which are now fixed. The increases the > chances that a plugin people write for 2.0 has a much bigger chance of > continuing to work in later releases. BTW, I encourage people who plan on > writing plugins to start playing with the current code, to see if there are > more weaknesses to be corrected. > > From now on, the subversion tree on Sourceforge will no longer be updated, but > you can follow all development here: > > https://code.launchpad.net/mnemosyne-proj > > 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 -~----------~----~----~----~------~----~------~--~---
