Hi all,
I agree that it's very helpful to see tasks in the calendar view. That's why we're planning to support something like this in our Android task app. Our approach is slightly different. We want to "sync" due dates and start dates of tasks into separate Android calendars (one for each task list). We don't want to overload the calendar UI with events for ongoing tasks, that's why we only add start and due dates as two different events. Later we may add a single all-day event that contains the titles of the ongoing tasks of that day in the event description, but I'm not sure if that's of any use.
cheers
Marten
Am 27.01.2015 um 07:15 schrieb Ján Máté:
Hi Johan,
I understand but I still not like this approach ... if there is something I need to do, I must see it not only today but also if I switch to the next week (especially if during the next week is the deadline). The question when I switch the view is: "what I need to do next week?", so there is no reason to not show the todo (if it is not completed).
Showing it only today is something like "you must to do it today", what is not true in general (because it has a deadline which is very probably NOT today).
JM
On 27 Jan 2015, at 16:04, Johan Vromans jvromans@squirrel.nl wrote:
Hi Ján,
5.) you change the view to the next week (2015-02-16 - 2015-02-22) => we must show the "floating todos" in the interface somewhere ...
I think this is where the misunderstanding comes from.
If a floating event has a starting date in the future, it should be shown only on the starting date. It behaves as an ordinary, future, all-day event.
If a floating event has a starting date in the past, and is not yet completed, it should only be shown on todays date. It behaves as if it were an ordinary all-day event scheduled today.
If a floating event has been completed, it is no longer shown at all. (Or possibly only on the date it was completed for archival purposes).
So if you change the view to next week, no floating events need to be shifted in confusing ways.
-- Johan