search

dmitrym0 / org-hyperscheduler

org-hyperscheduler is an Emacs package that helps you organize your day.
GNU General Public License v3.0
188 stars 14 forks source link

Show clocked time #10

Open wuqui opened 2 years ago

wuqui commented 2 years ago

Could you also display clocked time? That would be nice.

Cool package, thanks for your work :)

dmitrym0 commented 2 years ago

That's an interesting idea -- where would you like to see the clocked time?

👍

wuqui commented 2 years ago

In all calendar views. Basically the same way as in org-agenda, which doesn't only contain information on scheduled time blocks, but also the time one has tracked on past tasks.

dmitrym0 commented 2 years ago

Well, in the calendar the block designates the originally scheduled time.. I guess I could display clocked time as part of the event label?

wuqui commented 2 years ago

Well, I was imagining clocked tasks to get time blocks as well. So if you clocked emails from 09:00 till 11:00 and it's 12:00 now, the calendar would show a 2-hour block for this past activity.

dmitrym0 commented 2 years ago

Ahh gotcha that makes sense. It's more of a logging activity then. This doesn't really fit into my workflow, but if you're interested in creating a PR, I would be happy to accept it.

It should be fairly straightforward:

  1. modify the agenda filter to return clocked tasks as well
  2. on the calendar side, when processing inbound tasks, create a new calendar category (to visually separate clocked tasks from scheduled tasks) and maybe set tasks to read only so they cannot be modified in the calendar.
wuqui commented 2 years ago

Unfortunately, I don't have the skills to make this happen.

Besides, I have to say that I deactivated this package since I didn't like how it cluttered my files with all those tags and ID properties. I'd be happy to come back to should there be a new version with a different implementation. Could it use heading properties instead and scan all org-agenda-files, for example? Anyway, thanks again.

dmitrym0 commented 2 years ago

Unfortunately, I don't have the skills to make this happen.

You're an Emacs user so I beg to differ 😄

Besides, I have to say that I deactivated this package since I didn't like how it cluttered my files with all those tags and ID properties. I'd be happy to come back to should there be a new version with a different implementation. Could it use heading properties instead and scan all org-agenda-files, for example? Anyway, thanks again.

Yeah, I agree that it's not the best; there's #8 to track the tags, it's in the queue.

In terms of IDs, I'm not sure what can be done. Fundamentally, each entry has to be identified in order for changes from the calendar to make it back into Emacs. I'm going to remove the tags (per #8) and use the headings properties instead.

wuqui commented 2 years ago

Cool! I have subscribed to the thread and will keep an eye on it then 👍

dmitrym0 commented 2 years ago

Rudimentary implementation of this in feature/react-calendar branch.

One issue that I haven't been able to resolve yet is that I rely on scheduled/timestamped items first and THEN get their clocked items. As far as I've been able to find there's no graceful way of finding clocked in items for a given time period.