On Saturday 19 September 2009 11:18:40 am OldGrantonian wrote: > The whole purpose of such a hideous structure is that I can insert > other files, not related to Mnemosyne, that are specific to the > subject.
If they are not related to Mnemosyne, I'm not sure it's a good idea to try to impose the structure of one onto the other. If you really want, you could go one level deeper and give each mem file its own database, so that you can use the -d option. However, for 2.x, the recommended way is to put *all* your cards in a single database. There will be a much more sophisticated 'activate cards' dialog, where it's easier to activate previously saved sets of cards based on certain criteria. This is much more flexible than splitting these sets in separate databases: with the 2.x scheme, cards could belong to more that 1 set, and you could activate cards based on much more flexible criteria, e.g. grades. > This would allow the user to have different configurations and plugins > for each database. You could write the plugin in such a way that it behaves differently e.g. depending on the tags a card has. 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 -~----------~----~----~----~------~----~------~--~---
