Skip to content
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

Tool tips for due/threshold dates and recurrences #511

Open
dlaidig opened this issue Aug 28, 2023 · 5 comments
Open

Tool tips for due/threshold dates and recurrences #511

dlaidig opened this issue Aug 28, 2023 · 5 comments
Assignees

Comments

@dlaidig
Copy link

dlaidig commented Aug 28, 2023

You indicated in #224 that the tool tips should be tracked in a separate issue, so here it is.

My original comment was:

It would be quite cool if a tooltip would show something like "today", "yesterday", "in 5 days" or "27 days ago".

@warmwaffles added

Hover over tool tips could be used to add more clarity on stuff abbreviated. Food for thought.

In more detail:

  • Due dates, threshold dates, recurrences and possible other special items (pomodoro? not sure what else is there) should have a tool tip.
  • For me, the main functionality of this tool tip for due and threshold dates would be to show how many days the given date is in the future or in the past, so I don't have to do the math myself (or remember the current date...).
  • Maybe also adding the weekday would be nice.
  • For due dates, the tool tip should probably display the date of the next occurrence. (And maybe add some hint at how the recurrence specification is meant to be understood. I can never remember when to use the +.)
  • A title would be nice, especially for "threshold date" since "t:" is really not self-explanatory.
  • If you don't mind the tool tip getting a bit larger, maybe also add a one-sentence explanation of the respective feature in a small font.

(I'm aware this is not the most specific description. I was just trying to collect some ideas to potentially extend my original idea. Take what you find useful and ignore the rest.)

Copy link

This is an automated response. We acknowledge your report, and we appreciate your engagement. However, as there has been no recent activity in this thread, it has been marked as stale. If you have any further feedback or if the matter is still relevant, please do not hesitate to respond. Otherwise, this thread will be automatically closed in 15 days from now.

@dlaidig
Copy link
Author

dlaidig commented Feb 28, 2024

I think this is still relevant.

@ransome1
Copy link
Owner

@warmwaffles @dlaidig although not the exact solution for this request, you might want to check out the latest pre-release, it contains part of it, the conversion of dates to human friendly ones. It can be enabled in settings. We should be able to use the function to work out the tool tips here.

@ransome1 ransome1 moved this from Backlog to 2.0.12 in sleek 2.x Feb 28, 2024
@ransome1 ransome1 moved this from 2.0.12 to Backlog in sleek 2.x Mar 16, 2024
@dlaidig
Copy link
Author

dlaidig commented Mar 27, 2024

I've tested this a while ago with sleek-2.0.12-rc.3 and thought that I commented here but that apparently got lost.

My first reaction was "wow, this feature solves 99% of my personal use case" (while tool tips with more information are still a good idea). I was quite happy to see "t: 4 days ago" instead of a date. And opening the dialog to edit the task still allowed me to see the actual date.

Now I updated to sleek-2.0.12 and it shows me "t: elapsed" instead of "t: 4 days ago". This is really not useful since non-elapsed tasks are hidden anyway.

When changing the filter to show tasks with threshold dates in the future, I also noticed that for tasks with "t:2024-04-01" it shows "t: next month". I guess this is technically true, but it gives my brain the impression that I still have a few weeks before this gets relevant. I would rather prefer to see "t: in 5 days".

@ransome1
Copy link
Owner

@dlaidig I think this should be discussed in the feature request, where this feature has been established: #609

There has been a longer discussion going on, where you can see why the feature had been designed the way it is right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants