Oh, quickcollection, where art thou?

My comment wasn’t meant as condescending, and wasn’t even directed at an individual. I’ll spell out in more detail what I am getting at…

Last month there was a request for collections that would support arbitrary ordering, for darktable.

Today, there is a request for quick collections from arbitrary folders, for DigiKam and darktable.

At some point, someone is going to request something similar for, say, RawTherapee.

Does it make sense to independently add the same functionality to package after package after package, or does it make more sense to build a common collection manager that can pull together files from arbitrary directories and allow them to be put in an arbitrary order, and then get to the editing tool of choice via right click context menu? The latter would even allow inclusion of other types of files in the collection, such as article text, presentation slides, and so on.

1 Like

Don’t get me wrong. I think, it’s a nice feature worth to mimic because it may save some time.

But I was a bit upset by your mentioning of hundreds more videos, as I prefer getting to the point over quantity and I also don’t like this look at all the hundreds of other posts(videos), which confirm what I write stuff :wink:

Good point. And - much to your surprise - I’d agree.
I’d be happy to use just “one ring to bind them all”. Darktable OR Digikam, that is. But, alas, this is not possible currently.

.M

Yes, it is a time-saver. And a generally funky feature.

.M

Never mind.

.M

If you read my posts, you’d know that I did NOT use "“you need to have used LR extensively” as “explanation”. This is rabulistic BS.
Take care.

.M

You’re asking someone to do something for you. They asked you to clarify what you want, and explained why your request needed to be made clearer. And now you’re calling their response BS.

That’s not how we roll here.

5 Likes

Perhaps you would like to google the meaning of “context”.

.M

I’m sorry, this seems to be headed no where positive, so it is locked; it maybe unlocked in the future.

Please consider exactly what is being requested in terms of resources when making a feature request. An outline of what is necessary and general expectations are explained well in the answer to this meta StackExchange question: How do I write a good feature request?.

File feature requests in the correct place, not here.

When filing your request in the proper place, make sure you describe it adequately. Hint: “you probably can’t understand” is not it.

Ok, I should have read to the end before replying.

@paperdigits +1 for closing this.