[Design] Should we rename Dump and Reload?

[Pieter Hartsook]

I think a warning that ALL collections, accounts, etc. are going to be
replaced when you choose reload might be nice. I was a bit surprised
to find all my previous data gone when I reloaded with an obfuscated
dump. I was expecting an additive process instead of the destructive
replacement.

Pieter

On 5/2/07, Heikki Toivonen <heikki at osafoundation.org> wrote:
> Phillip J. Eby wrote:
> > 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"?
>
> File > Prepare for migration (was: dump)
> File > Migrate               (was: reload)
>
> ?
>
> --
>   Heikki Toivonen
>
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design
>
>
>