-
-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sort by multiple criteria (Call for testing) #135
Comments
Personally it would be great to have two 「Sort by」
|
@rzelnik , while looking into how to approach this feature, I was rereading your post @rzelnik. If sorting/grouping by due date first and then by priority is what you want to do, it should be possible already. If you change the sorting method to due date, the next sorting method will be priority. That only as a hint. The real feature of course is to make every possible combination defineable. Let#s see what can be done ;) |
Yes, I already noticed that when I sort by Due date, priority is the (hidden) second sorting option. The another drop-down menu for the secondary sorting option would be useful - it would be it clearer and easier to understand and it would add more customizability. However, one visible sorting option and one hidden/automatic is also good. |
@rzelnik , @nutnutwin , I added a first draft of this function to the latest pre release: https://github.com/ransome1/sleek/releases/tag/v1.0.7 At this point I could really need your support. If you can spare a bit of time please download it and give it a proper testing. I'm curious if this works well in your environment. |
Hi, @ransome1. I built my own AppImage for 1.0.7 and the multiple sort criteria feature seems to work for me. Very cool! However, I did notice one thing. If I drag on the "==" beside the criterion, it moves by itself without the criterion and leaves the criterion on a separate line. |
Why didn't it occur to me that you are using Sleek to task manage Sleek development?! :D A few notes/possible improvements:
|
Thanks for your feedback so far. If you're wondering, why the filter buttons do not work any longer; Please redownload the release ;) |
@9z0 , @nutnutwin . I replaced the drag and drop implementation with one that is a bit more joyable ;) @9z0 , I appreciate your suggestions, but I don't think I see the big benefits for the majority of sleeks users. sleeks approach in general is to keep the GUI as clean as possible. I rather make sleek a simple experience for 90% of the users than an overly functional one for 10%, that don't benfit or even confuse the 90%. But of course I understand that this is only my opinion and there will be plenty of users out there who disagree. |
No problem, although I think you underestimate the average sleek user! In any case, I still believe you should expose as much as possible in config files. These help the 10% and don't bother the 90%. I edited #151 to mention that aspect. However, I'd still recommend "sort by the todo text itself". |
@9z0 ah ok, now I understand what you are referring to in the other ticket. |
@9z0 I am not sure if it is about underestimating sleeks users, I am deeply convinced they wouldn't have ended up with todo.txt and sleek, if they would be below average. I assume the typical sleek user has tried out a couple of different todo(.txt) apps and was amazed on how unpleasant many felt like and how much complexity had been worked into some interfaces. I think he or she has no overly big motivation in figuring out how the app works and is in fact happy about the limited choices some apps offer. Not because they are not able to understand all those toggles, menus, buttons, etc., but because they need a simple helper that guide them to accomplish a simple task that can easily be done with pen and paper as well. Exposing settings in the config file is not a problem, especially if existing settings get removed from the GUI but stay active in the code. Implementing new edge case features and making them available in the user-preferences.json is totally fine, as long as those features are developed neatly, maintained and don't interfere with the major functionality. I personally rather focus my efforts on existing features or ones that benefit most users, but I am super happy to see that others are contributing edge case features, for instance the Sugar implementation, the extended recurrences or just today the first draft on the advanced text search. |
@rzelnik this feature has been released with 1.0.7: https://github.com/ransome1/sleek/releases/tag/v1.0.7 I am going to close here. If there are any issues with this feature, please report back here and we will reopen. |
I can also confirm that the setting in I removed the sort criteria that I don't want and sleek used the remaining ones and then in-file sorting as expected. 👍 |
It would be great to have two (or more) sorting criteria, for example Sort by Due Date and then by Priority.
The text was updated successfully, but these errors were encountered: