Moving photos between collections
Dariusz Duma
I can't figure out how Picty manages photos in collections. I can point directory, and it's collection, but how to add new photo to collection except coping it to the directory?
I think that moving photos between collections (tabs) is more natural way to manages them. Some ideas:
1. Possibility to add photo/photos/dir to opened collection(s), no matter where the photo is located. Picty should save collection as paths to the files (photos).
2. Moving photos between collections is nothing more, than coping paths between collections config file. Photos physically stay at the same location.
Why this is a good way to manage archives? Imagine, that you've plenty of files in dirs segregated by date/place/event. Moving files between dirs wastes first stage of selection - the date/place/event. Collections are the more visible way to organize photos by the theme (flowers/landscape/architecture and so on). The another stage are tags and categories.
Damien Moore
>Why this is a good way to manage archives?
> Imagine, that you've plenty of files in dirs
>segregated by date/place/event. Moving files
>between dirs wastes first stage of selection - the
>date/place/event. Collections are the more visible
>way to organize photos by the theme (flowers/
>landscape/architecture and so on).
As currently implemented, a local collection is a single directory (and its subdirectories). You can of course have more than one collection, but then you lose the ability to globally search your collection etc. Re grouping by themes, couldn't you stick with a single collection and just use a set of tags? I also added an "album" keyword that is linked to one of the IPTC keywords (iptc.application2.subject) that you could also use for this but I haven't added much GUI support for it yet.
It would be possible to make a collection type that supports multiple directories or even individually selected files, but that isn't implemented right now. There would be a few technical hurdles involved with doing this because some of the code relies on there being a single root directory. This might not be very robust because it would easy to lose track of images as stuff gets moved around in the filesystem. (The current implementation is also vulnerable to this.)
For now the only way to add images is to copy them into the directory containing its children. In case it wasn't clear, the ability to move and copy images between collections in the GUI is provided by the image transfer plugin, which puts a button on the main toolbar (look for camera icon) that pops up a modeless transfer window. In that window, select the source and destination collections (both need to be open) and any other options then click transfer selected or transfer all, which copies or moves the files. You should see a progress bar if it is working (though it won't be around for long if you only copy a couple of images).
So yes, it should be possible to implement what you are suggesting, but I would do it as a separate type of collection because I like current behavior for most purposes.
BTW, another way i could handle the issue of not wanting to copy images around is to add support for symlinks. Have you thought about whether that would do what you need?
--
You received this message because you are subscribed to the Google Groups "picty" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pictyphotomana...@googlegroups.com.
To post to this group, send email to pictypho...@googlegroups.com.
Visit this group at http://groups.google.com/group/pictyphotomanager?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.