+1 on the renaming of "Dump and Reload".
I prefer the pair "Backup/Restore" (which makes clear that current data
are wiped out) though I remember Andi had issues with those terms for
some database connotation those terms have.
Cheers,
- Philippe
Sheila Mooney wrote:
+1 on renaming Dump and Reload
Like PJE, I am not crazy about using the term "import". I like
"Migrate Chandler Data".
On May 2, 2007, at 11:54 AM, Phillip J. Eby wrote:
At 11:13 AM 5/2/2007 -0700, Mimi Yin wrote:
File>>
Import .ics calendar file...
Export .ics calendar file...
Import Chandler data...
Export Chandler data...
On the Import / Export Chandler data dialogs, can we add text
explaining what's being exported and imported?
+ Import all collections, items, accounts and sharing settings from
a file.
+ Export all collections, items, accounts and sharing settings to a
file.
Note that reloading, at least in the Preview timeframe, is not
required to preserve any *existing* data; it is allowed to delete the
entire repository and start over.
While I'm not overly attached to the dump/reload terminology,
"import" does not seem sufficient to imply that data loss will occur.
The intended function of dump and reload is to support *migration* of
Chandler data across Chandler versions or OS platforms -- it really
has no other function. Perhaps some names that have to do with
migration might be appropriate? Maybe a "Migrate Chandler Data" that
then has options to "replace all collections/items/etc. from a file"
and "write all collections/items/etc. to a file for migration to
another OS or chandler version"?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
