Re: importing directories

[Gabriel Burt <gabriel burt gmail com>]

On Wed, 2005-11-30 at 20:35 +0000, Sam *Turtel* Barker wrote:
> I don't see where you can lose data from changing the setting surely
> what is imported already will stay as it is and anything new goes to
> this directory. Having the directory stuck as ~/Photos really doesn't
> suit what I would like as my structure, I use /media/images/ and have
> f-spot dealing with everything within that. A good compromise would be
> to have it as build setting, by default use ~/Photos but a flag passed
> in at build time could change it. Any one have any preferences?

I don't think any of these settings should be build time thing.

Photos you have already imported are not at risk, the risk comes from
the user not remembering that last time they chose not to copy and this
time they need to.

Having the directory F-Spot copies photos to be customizable is a good
thing, and even necessary (for obvious translation reasons).

> I'm not keen on the idea of two dialogs, I think having one dialog
with
> a check box saying copy to enabled by default for anything known to be
a
> removable device and persistent for ant other folder would be best
This
> is possibly what is had with the CVS version but I only have 0.13
> currently to base opinions from.

Except there's the case that someone does want their existing, hdd-based
directory structure copied into F-Spot.  I'm not sure of the best way,
but we want to make sure we provide intuitive ways of letting the user
do their tasks quickly and without frustration, while prevent them from
making mistakes due to a confusing UI.

Gabriel Burt