Tim Retout wrote: > On Wed, 2008-04-30 at 09:39 -0700, Bill Moseley wrote: >> Dates in the database should not be floating, but based on some >> timezone. > > Agreed...
Disagreed. There is no such thing as a "floating date". The timestamp is there, and stays unaltered. In the 99% case, it is based on the timezone of the camera. >> Since EXIF doesn't have a timezone associated with the timestamp on >> the image isn't the only possible solution to ask the use at import >> what timezone the camera is set for? > > I can't think of a good user interface for this - if there are different > timezones in the same import, it becomes complicated. That's not to say > that it can't be done. Don't need one. 1) Import photos. 2) Select the ones out of order. 3) Adjust time 4) Shift by x number of hours. This is not rocket science, a user will do this if they want to. Adding timezones complicates this. > 1. Assume that the camera was using the same timezone as the > computer is set to. This is probably the most common case. Done. > 2. Provide a mechanism for users to change the timezone of photos > after import. They can. Time shift. Anything else is superfluous to the 99% case, because the user cares about the timezone their computer is in. Almost no one on their trip to Paris will care that they took the photo at 14:00 Paris time. Their computer will show it as 09:00 EST and they'll be happy. Order preserved. > 3. Require users to purchase a camera that supports XMP and > timezones. (I assume these exist?) "In the future there will be robots." --Pat _______________________________________________ F-spot-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/f-spot-list
