[Bug 658175] Re: Shotwell: display ~/Pictures by default

[Ugo Riboni]

Everything not explicitly commented below is either acknowledged or
already done.

> After thinking about this some more, ideally we'd want usb key to work just like plugging in a camera.
> That is, it would be great if usb key showed up in tree view and user could browse their photos from
> key but not be able to import them. Could you look into the amount of work necessary to make
> this happen?

The functionality is already there to show USB mass storage devices as "cameras" in the left tree.
The way it works though seems to be that it will detect the USB disks as a camera only if it has a "DCIM" folder on its root. I think according to the de-facto standard mentioned here:
http://en.wikipedia.org/wiki/Design_rule_for_Camera_File_system , though i didn't do much further research on it.
All of this happens through libgphoto automatically, as far as I can see.
Of course if you want to have any arbitrary USB stick with jpegs scattered on it to appear as a camera, then I imagine it is still doable but can get a bit complicated as you have to create an alternative camera detection path that doesn't use libgphoto. I can look into that if needed, but IMHO it's good enough to show as cameras the sticks that are really from cameras.

> But if you plug in a usb key and choose file import, and navigate to usb key and choose
> the folder from the usb key, you are prompted with a dialog that asks if you want to 
> "Copy into Library" or "Create Links".

Correct. That happens since the key is already also mounted "normally",
so it's just like importing any other directory in any other mount. This
is a bit moot though, since we removed all the options allowing to
import arbitrary files, per your initial request, so we can't really get
to that dialog anymore.

> ~/Pictures will in fact be mounted read-only

Then I suggest we keep ~ as the library location (and not allow the user
to modify it via the configuration UI), but do the initial automatic
import run on ~/Pictures. It seems much safer this way in the case
there's some data that gets written to the library location we don't yet
know about (I did look only into a small subset of the source after all)

> We need to make sure that duplicates are not added when rescanning on
each startup too.

Shotwell's import features already takes care of this automatically.

-- 
Shotwell: display ~/Pictures by default
https://bugs.launchpad.net/bugs/658175
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Canonical OEM Projects.