From: Ant <34...@t8...> - 2004-07-07 22:27:09
|
Hello Alex, Notwithstanding the email I've just sent, I think that you confirm here what I thought was the question, if you see what I mean - the first of your options seems right to me as indicated below. Having said that, I don't use Gramps as - deeply? - as some people will, so I'm happy with the majority or your decision! And thankyou again for your and others' efforts. Regards Ant * Support UKIP - Don't let the EU rule Britannia! * On Tue, 6 Jul 2004, Alex Roitman wrote: > Thanks to everybody voicing their preferences concerning Save-as/Export > options. > > An important observation that can sway one's opinion is the following. > In most software, "Save as" means actually two things: (1) save the file > I'm editing right now under another name, and (2) continue editing this > newly written file, so that future changes go into this file. > > As opposed to this, Export has a clear annotation to "write and leave it > alone" type of action. New changes go to the same file that was edited > before export. * The option above, for me. * > > We can easily implement traditional "Save as" with the native format. > However, to create GEDCOM and then import it right back to continue > editing will possibly cause data loss (not all gramps fields have GEDCOM > analogs). Besides, it would require setting up a new native database > anyway, so the whole thing would be convoluted and awkward. The bottom > line is: we can only continue editing the native format after saving > under another name. > > So, if we want to keep parallels to most of the existing software then > "Save as" should only be used for a native format. > > "Save a copy" does not have this "continue editing new file" > association, so "Save a copy could potentially be used for all formats, > both native and non-native. > > Same is true for export, except calling native-format-save an "Export" > is kinda awkward too :-) > > In light of the above dilemma (or is it already trilemma? :-), would > everybody be OK with "Save as" for the native "save and continue > editing" and "Export" for all other formats? Optionally, Export can > become "Save a copy", in which case it can also include saving (and > laying away) native format. > > I know I'm pushing it, but could you please indicate whether the above > makes sense and whether my suggestion is acceptable. > > Thanks, > Alex > > -- > Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html > Dept. of Neuroscience, Lions Research Building > 2001 6th Street SE, Minneapolis, MN 55455 > Tel (612) 625-7566 FAX (612) 626-9201 > |