> > I do not see a contradiction between using spaced repetition, which I want, > > and preventing access to decks. You fail to explain how those two concepts > > naturally exclude each other by their very nature. > > There may be some confusion as to what "write access" means. ... SNIP ... > From an application perspective, you might be thinking of "write > access" as the ability to add/remove/edit the contents of a "deck".
Exactly. I'm pleased someone understands this, besides the original poster. As I said, denying the *program* access and denying the *student/user* acccess are not the same thing, which is why the different data types do not have to be in a different file. The control can be blocked at the level of the GUI, and the OP didn't ask for anything more than the optional removal of the editing facility. It was others, not him, who made assumptions that revealed their ignorance. > Part of the larger sense confusion here might be that Mnemosyne trusts > that users are mature enough do the right thing. Yes, that is true. But the extra programming involved in providing a lockdown would not actually be that hard - an evening's work, perhaps. I don't write python, or else I would submit a proof-of-concept program to demonstrate. I suspect there would be less new code than there have been lines in this thread. In Java, it took me about 40 minutes for my own program, where the access issues are exactly the same, and the content/scheduling data are still within the same file after I made the changes. I will probably remove the 'Lock' facility from the default GUI, because I agree most adults won't want it, but I will provide teachers a simple way to add it if they do want it. The value of a lockdown might be greater than you think, in the school setting. My own kids use my program to learn German, and they have all at some stage added joke cards to each other's vocab files. These were single cards that were designed to be a surprise, and they were deleted after they had their desired effect. No harm was done, but I thought of locking the files at one stage. I didn't because the joke staled rapidly, they are generally well-behaved children, and I wanted them to be able to add their own content. I can easily imagine that a school bully would take it further. In a highly developed, tried-and- tested curriculum, the need to add new cards might be fairly limited, and so the value of locking the decks to remove one source of headaches might be greater. It would have ZERO impact on the ability of the program to perform its scheduling function. Craig. -- 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=.
