Re: [Memaid-devel] Announcing the Mnemosyne Project

[Peter B. <Pet...@ug...>]

On Saturday 11 February 2006 04:49, Bruno Vernier wrote:
> Some notes (after one day of use):
>
> 1.  whenever i launch mnemosyne, I get a non-critical warning:
>
> /usr/lib/python2.4/site-packages/mnemosyne/core/mnemosyne_core.py:46:
> SyntaxWarning: import * only allowed at module level
>   def initialise():
>
> does anyone know a quick fix before i start researching it

=46ixed in CVS, thanks!

> 2. I changed the changeover time from 3:30 to midnight by editing line 199
> from:        self.time =3D time.mktime([t[0],t[1],t[2], 3,30,0,
> t[6],t[7],t[8]])
> to:            self.time =3D time.mktime([t[0],t[1],t[2], 0,0,0,
> t[6],t[7],t[8]])
> would it be worth it to anyone for me to patch mnemosyne to make that a
> configuration variable?
>
> 3. I copied the function process_answer into a new function
> process_answer_fake and removed anything that writes into the database in
> order to use it to show what each of the grades would mean in terms of
> interval length, like this in mail_dlg.py:
>
>   future_intervals=3D"0:%s 1:%s 2:%s 3:%s 4:%s 5:%s"%(
>               process_answer_fake(self.item,0),
>               process_answer_fake(self.item,1),
>               process_answer_fake(self.item,2),
>               process_answer_fake(self.item,3),
>               process_answer_fake(self.item,4),
>               process_answer_fake(self.item,5)
>               )
>         self.answer.setText(escape(self.item.a+future_intervals
> ).decode("utf-8"))
>
> again, is this something worthwhile submitting as a patch?

As for 2 and 3, these seem fairly specialised and not of great use to the=20
ordinary user. But if geek-oriented people want this, you can always send a=
=20
patch to them privately.

Note that I would like to have the interface of Mnemosyne as clean and simp=
le=20
as possible. I'm personally quite horrified by the tangled mess that is e.g=
=2E=20
SuperMemo.

> 4.  things that I intend to work on (unless someone beats me to it) is
>
> - displaying how many items will need to be revised the next day, days,
> next week, weeks, next month, months, next year, years

That sounds useful! Note that there's a whole lot more of statistics that c=
an=20
be displayed based on the log files, but I haven't concentrated on that so=
=20
far. The challenge is to present all that info in a clean way that doesn't=
=20
clutter the user interface too much.

> - automatic resizing of items back to default size after a large item has
> been shown
> (currently it adjusts in size for larger items but never reduces back...
> which is a minor frustration for me)

What exactly are you talking about? Mnemosyne is not supposed to resize ite=
ms.

> - some way of doing mass editing when I want to rework entire sections or
> categories ... i tend to create items on the fly and later realize they c=
an
> be done better or consolidated or split up etc... but I want to see them
> all at once and edit them all at once database or spreadsheet like

You're not the first to request that feature, so it's definitely very usefu=
l,=20
like being able to select multiple items in the list, right clicking, and=20
choosing 'Change category'.

Thanks for helping out!

Peter

PS: I've created a mnemosyne-devel-list, please use that in the future.

=2D-=20
=2D-----------------------------------------------
Peter Bienstman
Ghent University, Dept. of Information Technology
Sint-Pietersnieuwstraat 41, B-9000 Gent, Belgium
tel: +32 9 264 34 45, fax: +32 9 264 35 93
WWW: http://photonics.intec.UGent.be
email: Pet...@UG...
=2D-----------------------------------------------