From: Bernd S. <sc...@gm...> - 2001-12-31 05:40:39
|
Thinking about the new "Enable LDS tab" option, I had an idea: How about having "Program settings" and "Database settings"? The "Enable LDS tab" option would be a "Database setting". This way, the open (or import) mechanism can check for LDS data and (in case there is any and the LDS option is not set) bring up a warning along the lines "LDS data was found. Should the LDS tab be enabled for this database?" I don't see too many database specific options yet but it might change. Here are my ideas: - Show LDS tab - Display attribute on Edit Person window (BTW, if the option is not set, shouldn't its input field be disable?) - Default report/web site directory Maybe also: - Do not display alternate names in person list - Revision Control In order not to have to enter all the options for every new database, there could be a button in the option dialog saying something like "Import options from existing database..." What do you think? Bernd -- Bernd Schandl Tired of spam? Use spamcop.net to complain! |
From: Don A. <dal...@us...> - 2002-01-03 17:52:07
|
On Sun, 2001-12-30 at 22:15, Bernd Schandl wrote: > Thinking about the new "Enable LDS tab" option, I had an idea: How about > having "Program settings" and "Database settings"? The "Enable LDS tab" > option would be a "Database setting". This way, the open (or import) > mechanism can check for LDS data and (in case there is any and the LDS > option is not set) bring up a warning along the lines "LDS data was found. > Should the LDS tab be enabled for this database?" Right now, all the settings are global. There are no database specific settings (that is, having one set of settings for one database, and another set for a different database). I am open to changing this if we feel it is necessary. -- Don Allingham dal...@us... http://gramps.sourceforge.net |