OK, I think that adding some number after folder name is better way to resolve conflicts than my renaming chains. There are now two open questions: 1) Using visible name as default identifier whenever possible. 2) Using simple numbers (2, 3, ...) instead of longer identifiers.
As for the second issue, I think it is simpler, because you have to check for duplicates anyway. Long message ids are used when there is no way to check for uniqueness. On Tue, 8 Jul 2003 18:48:26 +0200 Xavier Nodet <[EMAIL PROTECTED]> wrote: > > > > I think this can cause problems with imap folders and future > usenet > > > > news support. > > I do not see the point, here. What is the relation between the fact that > there are many possible news folders, and IDs? My news server carries more than 100k newsgroups. If you generate Id for each one, my configuration file grows to 10MB. It's true that groups cannot be renamed on server (well, not right now) and it doesn't make sense to rename them locally, but you don't want to complicate things by splitting identification task between server's identifier and group name. In this situation, it's important to keep default settings for group empty so it doesn't have to be stored until user does something with it. > > OK, MovedTo -> Name, MovedFrom -> Id. But then, MovedTo/Name is stored > > outside of folder's section (where most properties are located). Maybe > > NameForThisId, I am not sure. As I accepted idea of numeric identifiers, I think the above can be simplified into singe Id property. Mahogany then scans whole configuration for these properties and it can then tell name from Id. > > > > Preferences are full of folder references that should survive > > > > renaming. > > > > > > Preferences are just the set of values stored for a particular > > > folder. And if one is not found in the set of values for a > > > particular folder, one looks for it in the parent folder (but this > > > reference to the parent folder is not stored in the folder profile > > > itself). > > > > Yes, I know this. I meant for example list of folders opened at > > startup or which folder is used for trash. > > Any and all properties like that are to be changed via the GUI. And the > GUI will show you the names, not the IDs. Yes, I was replying to something you said about references appearing only in filters. > [filter1] > if (subject is "...") move to junk-2003-07-08-18-44 > > [junk-2003-07-08-18-44] > Name=junk > Type=local-file There is something unusual about this. You are storing properties under identifier. This would require changes to code that reference folders by visible name. Using timestamp provides little advantage when you have to check for duplicates. Simple numbering scheme would be also easier to read. Your example should look like this: [filter1] if (subject is "...") move to junk2 [junk] Id=junk2 Type=local-file This assumes there is already some folder using Id=junk. Otherwise it should look like this: [filter1] if (subject is "...") move to junk [junk] Type=local-file ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
