A slight refinement is to allow drag and drop from task to event with default setting of busy so time-blocking can occur. Also allow setting to either change from task to event OR duplicate as event. This is a standard practice for many time management, that is the habit of grouping tasks into a time block based on merely time or location or another context. For now, just worry about time. It is also key to Agile methodologies when standups look to that backlog (some in your tasks for the day) and look to time-box the activity, if it's self contained, or at least time-box the next step and break it up into multiple steps. That might mean allowing easy adjustment of time commitment, e.g. 1 hour, 2 hour, 3 hour, etc. by dragging a cursor on the size of the box (not unlike Google Calendar today). Finally, allowing the reverse might also be nice if you unable to do the task in the time-box allotted and have thus reprioritized for another day, but aren't sure which day yet.
Harvey Andruss
A slight refinement is to allow drag and drop from task to event with default setting of busy so time-blocking can occur. Also allow setting to either change from task to event OR duplicate as event. This is a standard practice for many time management, that is the habit of grouping tasks into a time block based on merely time or location or another context. For now, just worry about time. It is also key to Agile methodologies when standups look to that backlog (some in your tasks for the day) and look to time-box the activity, if it's self contained, or at least time-box the next step and break it up into multiple steps. That might mean allowing easy adjustment of time commitment, e.g. 1 hour, 2 hour, 3 hour, etc. by dragging a cursor on the size of the box (not unlike Google Calendar today). Finally, allowing the reverse might also be nice if you unable to do the task in the time-box allotted and have thus reprioritized for another day, but aren't sure which day yet.