After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 353074 - Provide a distinction between external photos and photos in the library
Provide a distinction between external photos and photos in the library
Status: RESOLVED INVALID
Product: f-spot
Classification: Other
Component: General
0.1.11
Other All
: Normal enhancement
: 0.7.2
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-27 08:52 UTC by Anders Conradi
Modified: 2010-09-17 05:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Anders Conradi 2006-08-27 08:52:13 UTC 
Since F-Spot is able to both catalog external photos and import the photos into the F-Spot library I think there needs to be a way to see which photos are kept in the library and which are only catalogued, but kept somewhere else.

Perhaps a tag or pseudo-tag that gets added to all external photos.

For external photos it would be nice to have a way to import them into the library .
Comment 1 Duncan Lithgow 2008-07-18 22:23:01 UTC 
From Launchpad: https://bugs.edge.launchpad.net/ubuntu/+source/f-spot/+bug/249463

Binary package hint: f-spot

Ubuntu 8.04
f-stop 0.4.3.1

Using the word 'import' in f-stop to describe both importing file (and 'registering' them) and 'registering' a set of images without importing them is confusing for me, let alone users new to the system and/or with English as a second language.

Can I suggest that these two fundamentally different ways of handling image files are keep distinct?
Comment 2 Ruben Vermeersch 2010-08-03 14:49:40 UTC 
Everything is in the library, whether you copy the files or not.
Comment 3 Duncan Lithgow 2010-09-17 05:51:15 UTC 
Hi Ruben. Okay so everything is in the library, but the fact that it's registered in the library does not mean it has been imported. Perhaps importing data into the library should be called registering instead of importing. I still regard this as a usability bug.