[Shotwell] Use cases of shotwell

[pt]

On 26 August 2011 20:54, Clinton Rogers <clinton at yorba.org> wrote:
> Ah, got it.  What you're seeing is that the event is being changed such that
> the start point of the event is the wrong date, when what you were expecting
> is that either the photos and/or videos you moved into the event would get
> their own (wrong) dates set to the (correct) date of the event, or, if
> nothing else, the date of the event shouldn't change.
>
> While the event date not changing would most likely confuse a lot of users,
> it certainly seems like the first option might be useful in a lot of cases,
> particularly for people with a lot of undated photographs (for example,
> someone with a large collection of scanned prints or slides), and I'll bring
> it up with the team here for discussion.  In the meantime, though, it is
> possible to control this to a limited degree by manually setting the date
> and time (via Photo -> Adjust Date and Time...).

It seems to me that we should drop the events altogether, or at least
make them independent from the date of the pictures, and have a
time-line instead.

With hierarchical tags, one can just use tags instead of events:
independent from the date, and with the possibility of creating
'collections', even nested ones (eg: Australia -> Trip to Uluru, or
Birthdays -> John's birthday and so on).

>> 2. I decided to create collection "wallpapers" for my desktop wallpapers.
>> It was in "Undated" when I created it (and filled with wallpapers). I added
>> there another wallpaper just now that has date in it's metainformation
>> somehow and the whole "wallpapers" event just jumped to folder "2002 -> July
>> -> Wallpapers".

Perfect example of how 'tags' outperform 'events': just tag your
wallpapers with a 'wallpapers' tag, and you have your collection
ready.

> Again, setting the date manually will control the jumping around somewhat,
> but you're right, this is far from perfect.

Again, we should have a time-line (photo's exif date, that should be
manually modified when wrong) and tags used to mark events (not moving
around when you add a photo with a different date).

> If I've understood correctly, the upshot of all this is you'd like to be
> able to force an event to not move around, even if there's a photo with a
> different date put into it, and not have to worry about manually setting the
> date each time.  I'll mention this to the crew here and open a 'feature'
> ticket for it - it might be helpful to have an option somewhere in the menus
> for locking an event to a date (or even undated, if the user so desires)
> somehow.

IMHO the way to go is to separate events from dates.

For what I see the events as they are now are just a (fixed)
hierarchy, like a folder tree in a file-system. For me they are a
time-line with a confusing name: I never change an event name to
something like 'trip to Paris', because we have tags for this. Plus,
there are obvious problems with reoccurring events, like birthdays,
that are simply not manageable with the current system.

Just my 2 cents.

Ciao ciao,
Piergi
-- 
Web: http://traversin.org
GNU/Linux user 190604