David Grundy wrote:Suppose I have a whole set of images. I decide to create a black and white version of each of them for a project, using an automated process in Photoshop, and I want to associate each of the new B&W files with the original images as versions. How can I get all of these Black and White versions to end up in a custom-created "Black and White" placeholder? I don't see how this can be done except by reassigning the placeholder for each image individually.
Whereas with the facility to apply a version placeholder change to a whole set of images, this could be done in a single operation.
Hence Concern #1: How to reassign image placeholders for batches?
At the moment it feels to me as though the versioning implementation is unfinished. You can get files associated with each other, but I don't see a sensible way to manage the versions and placeholders for sets of images. As far as I can see at the moment, if you make a mistake as to which is the main version when importing a bunch of files, the only way to fix it is to remove all the accidental main versions from the database, and reimport them is subsidary versions. And as mentioned above I don't see any way to make sure that newly imported versions end up with the correct placeholder.
Hence Concern #2: It will be hard to fix versioning mistakes.
In the example above, I don't see any way to get the B&W images associated as versions of the original images in the first place. Most likely, the files selected for the B&W project are dispersed across many directories - specifically, they will come from different years and months, so they will be in different folders on the disk. The only plausible way to get the B&W images associated with them seems to be to make sure that my automated Photoshop process outputs the B&W files in subfolders of the individual original files. Otherwise the "subfolder" versioning approach currently implemented won't work for these files. But this is not how I work - rather, the new files from the automated Photoshop process are always output to a single specified folder, so that I have the chance to check them over. This prevents some sorts of accidents where Photoshop actions don't work as expected, and specifically it ensure that my master image folders don't get cluttered with mistakes or unfinished work. I do not want to change this part of my workflow. I would rather abandon versioning.
Hence Concern #3: the subfolder versioning approach seems to require me to change the way I organise my files, in a way that reduces my protection from processing mistakes.
I am hoping Hert is just waiting for a bit more discussion before implementing a more complete and flexible versioning solution. The current approach is superficially simple but is actually complicated because of the time needed to work out how to do things within the imposed limitations. In fact it's sufficiently limited that I think it would be better for me not to use versioning at all. In which case I wonder why I need PSu ...
At this stage I have two days left of the PSu trial and I haven't yet reached the point of being convinced. It's nearly plausible ... but it just doesn't yet do enough. I don't see the justification for changing my file organisation completely, just to get an inflexible sort of versioning implemented.
Again I would say that I think this is a "false simplicity": important capabilities are not (yet?) available, and this makes the use of PSu more complicated in practice. A well-designed dialogue which makes it clear exactly what will happen is much simpler to use than a minimal dialogue where we have to guess what will happen, and design workarounds to get the behaviour we want. Perhaps the whole versioning thing should be seen as "advanced" and could be disabled until a user decides to deliberately enable it in the preference. Or, as suggested for some labelling features recently, have the ability to click on an icon somewhere (in a basic dialogue box, or elsewhere) that brings up a full-featured versioning dialogue.