Darktable: Sort collections descending

[GrahamByrnes]

If like me you prefer using the folder view in collections, there are two issues:

1. It sorts ascending, so if you have folders of the form 2020-03-23, your most recent work is at the bottom. This could also apply to the filename view;
2. Folders always start from "Users", so there are a couple of tree levels to traverse (ie Users/Graham/Pictures) before getting near photos.

So it seems to me it would be useful to allow ordering of the tree to be descending, and to somehow specify the starting point of the tree.

The first would be relatively easy, but not that easy, since "SQLite doesn't know about paths" to quote the comment in the code.

The second might not be so easy, I don't know yet (and "easy" being relative to my competence).

Does this seem desirable to some of you?

[johnny-bit]

Have a button to sort lists in collection asc/desc and make it universal and we're good :)

[GrahamByrnes]

Would you settle for a darktablerc asc/desc choice?
Then you can convert it into a button :-)

Le lun. 23 mars 2020 à 22:09, Hubert Kowalski [e-mail] a
écrit :

Have a button to sort lists in collection asc/desc and make it universal
and we're good :)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/darktable-org/darktable/issues/4543#issuecomment-602857459,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN2X2RXJYRT72LFBNPN2T6TRI7FZZANCNFSM4LSDPRLQ
.

--
Graham Byrnes
Bron (Lyon), France
Mes photos: https://500px.com/grahambyrnes

[johnny-bit]

hmmm... nah... for some collections current order is OK for others I'd sort
them differently...

button would be fine, but I doubt there a glyph that could be used so you'd
have to also add glyph for that :)

pon., 23 mar 2020 o 22:14 GrahamByrnes [e-mail]
napisał(a):

Would you settle for a darktablerc asc/desc choice?
Then you can convert it into a button :-)

Le lun. 23 mars 2020 à 22:09, Hubert Kowalski [e-mail] a
écrit :

Have a button to sort lists in collection asc/desc and make it universal
and we're good :)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/darktable-org/darktable/issues/4543#issuecomment-602857459
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AN2X2RXJYRT72LFBNPN2T6TRI7FZZANCNFSM4LSDPRLQ

.

--
Graham Byrnes
Bron (Lyon), France
Mes photos: https://500px.com/grahambyrnes

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/darktable-org/darktable/issues/4543#issuecomment-602859718,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACRRKFOXFHDIAGQ3RN4KJF3RI7GMRANCNFSM4LSDPRLQ
.

--
Pozdrawiam,
Hubert Kowalski

[TurboGit]

Have a button to sort lists in collection asc/desc and make it universal and we're good :)

But you'll need also to store the per collection sort choice into darktablerc to restore the sort when restarting dt.

[johnny-bit]

Yes! And single button will do + @TurboGit is spot-on with "remember sort order per collection" deal. But hoooo boy, this would really be positive thingie!

[GrahamByrnes]

Ok, we just took a vote at our work-breakfast-zoom for how long confinement will last in France... I may well have time :-(

[GrahamByrnes]

In fact I learnt something: there is this function that looks for a common path, and uses it to root the tree. So the reason my tree was rooted to c:/ was that I had a couple of photos I'd looked at once in drop-box.
Once I removed those, the tree re-rooted to pictures/ :-)

So it could be that part 2 is just a question of maintaining one's image files. Or, maybe some sort of folder-based version of @johnny-bit database maintenance... or just a comment in the manual.

The problem is that there is so much stuff in the code, that a comprehensive manual would either never be read, or would need to be a very terse man-style document.

[johnny-bit]

The problem is that there is so much stuff in the code, that a comprehensive manual would either never be read, or would need to be a very terse man-style document.

The manual problem is complex one. You actually need couple of different manuals:

1. user-scenario focused one, eg "how to do x"
2. usage generic focused one, eg "this is lighttable, this is import module that does this and that"
3. reference one, eg "this is split toning module, this slider does that, values this that etc"
4. technical one, eg "white balance module works like this, have fun equation"
5. code one, eg: "dt_gui_whjatever params x - amount of ffsdf..."

It's huge amount of work :) 5th one could be tackled by introducing something like requiring Javadoc-like comments in the code. 4th one could be worked out as a part of reference. 1&2 can be realized like Bruce Williams videos. the 3rd one is the hardest imo.

[GrahamByrnes]

Maybe encourage programmers to add a paragraph of comment at the top of
each program they work on?

Ideally maybe three:
a) What this does
b) How it fits into the general scheme (ie what calls it)
c) How does it do it, with a very rapid tour of the principal functions.

Then at least someone trying to change stuff would have some orientation.

There would be the usual Wiki type issues of people who understand least
having the strongest opinions... humans are complicated.

Le mar. 24 mars 2020 à 11:21, Hubert Kowalski [e-mail] a
écrit :

The problem is that there is so much stuff in the code, that a
comprehensive manual would either never be read, or would need to be a very
terse man-style document.

The manual problem is complex one. You actually need couple of different
manuals:

1. user-scenario focused one, eg "how to do x"
2. usage generic focused one, eg "this is lighttable, this is import
   module that does this and that"
3. reference one, eg "this is split toning module, this slider does
   that, values this that etc"
4. technical one, eg "white balance module works like this, have fun
   equation"
5. code one, eg: "dt_gui_whjatever params x - amount of ffsdf..."

It's huge amount of work :) 5th one could be tackled by introducing
something like requiring Javadoc-like comments in the code. 4th one could
be worked out as a part of reference. 1&2 can be realized like Bruce
Williams videos. the 3rd one is the hardest imo.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/darktable-org/darktable/issues/4543#issuecomment-603153224,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN2X2RQSE3F37VE7JRW6YHDRJCCS7ANCNFSM4LSDPRLQ
.

--
Graham Byrnes
Bron (Lyon), France
Mes photos: https://500px.com/grahambyrnes

[johnny-bit]

Maybe encourage programmers to add a paragraph of comment at the top of each program they work on?

@TurboGit - can you & senior devs consider whether it would be beneficial to general contributors to "suggest" adding doxygen comments to the code? Most IDEs support those and would probably speed up dev time and solve point 5 I mentioned about docs ;)

[GrahamByrnes]

Progress to date: can flip the order of folders, filmrolls and tags.
Despite changing the order of selection and the order of listing, cannot change the order for time or date. Seems to be a conflict with stuff going on in collection.c, whereas the tree-building of the collect lists happens in collect.c
No glyphs yet :-)

Edit: ignore the comments about collection.c, they just result from a variable for ordering collections, not lists of things in them.

[GrahamByrnes]

I think we're nearly there.

Part of the problem appears to be that things were added to collect.c without really thinking of where they should fit in. In practice, I think it's highly convenient to be able to flip the sort order of time-related variables: eg folders, filmrolls, time and date.

It might occasionally be nice to be able to flip the order for the other variables because you are specifically looking for photos of zebras, but this is more of an incidental issue.

So for the moment I've added a single order-select variable to flip folders, filmrolls, time and date; but not for anything else. It's accessible under gui/miscellaneous in settings.

Case

Other thing: default ordering also takes into account capitalisation, so zebras < Aardvarks < Colibris.
Maybe if you're a precise typist when adding tags this is useful, I found it annoying. So I changed the sort order to be independent of case. If this is potentially annoying to you, I could be persuaded to do something less normative.

[github-actions[bot]]

This issue did not get any activity in the past 30 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[GrahamByrnes]

Done