[Shotwell] Accessing an alternative database

[Brian Candler]

On Mon, Jan 03, 2011 at 05:10:50PM -0800, Jim Nelson wrote:
>    Anyway, that's my brain dump about all of this.  Solving your immediate
>    problem of creating a shared library writeable by two accounts is not
>    something I think can be solved at this time.  One possibility (off the
>    top of my head): create a dummy shotwell account and sudo to it to run
>    Shotwell.  This might introduce other complications but might solve
>    your immediate problem.  (Test this with data you can afford to lose,
>    obviously.  I've not even tried it.)

Thanks for the response.

I guess another way I could get 'read-only' access to a different collection
is to make a temporary copy of remote .shotwell dir, and then run
shotwell -d <tempcopy>. That's fairly ugly, but maybe it would be a
reasonable thing for shotwell to do automatically if it sees that the -d
target is not writeable.

My wife is non-technical, and I think it's a reasonable requirement for her
to be able to browse photos I took on my camera.

At the moment she just uses Nautilus to browse the originals in my home
directory.  This works OK as long as I'm manually classifying photos into
event directories (which is a pain for me).

While I was experimenting with shotwell, photos were going into YYYY/MM/DD
directories, which meant it was very hard for her to find a particular photo
- a ton of directory surfing was required.

So another solution would be for shotwell to reorganise photos dynamically
into a user-defined hierarchy, e.g.  YYYY/Event.  I think there's a ticket
for that too.

Regards,

Brian.