On Tue, 27 Jan 2015 12:01:23 +0100 Ján Máté jan.mate@inf-it.com wrote:
So if you have 100 todo items (real scenario in our company) then you will see 100 squares in for every day in the month view.
First, I would personally not apply this to each and every todo item, but only to selected items.
Another approach is to use "floating" squares and show the todos only for today,
Yes, that is why I introduced the "floating events" for this purpose.
but it will cause another problem with the interface consistency, because in the month view you will see todos only in "today" square,
Yes.
but if you switch to week view (e.g. next week) we must show these todos also in this view
Yes.
(=> inconsistent because in month view you see todos in different day than in the week view).
This I do not understand. In either case, the item is shown on the same day.
Also in both cases the interface will look terrible (and will be nearly unusable) with huge number of todos.
That is true; see my first remark.
What we can do (in one of the future releases) is group todo items and show something like:
[today]
- item 1
- item 2
[next 3 days] ...
will it help to solve your problem?
First of all, it's not a problem -- it's just a feature request :) .
Let me propose a slightly different approach.
For todos, it would be helpful if it were possible to show a compact list of todos in the calendar view. For example instead of the list of calendars, or possibly below the list of calendars. This would give a good 'first glance' view on what is currently important.
For thid list of todos, the grouping as you suggested above could be useful.
Additionally, add floating events. A floating events is similar to a todo -- it has a starting date and end date [Note: no times]. It shows up in the calendar at the starting date just like an ordinary (full-day) event. When the current date passes the starting date, the event is shown on the new current date. When the current date passes the end date the event should be shown in an emphasised way. A floating event does not disappear from the calendar view until it is explicitly completed (or deleted).
Would that be easier to implement and solve the inconsistencies?
Attila, would this work for you?
-- Johan