After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 581053 - Calendar tweaking
Calendar tweaking
Status: RESOLVED DUPLICATE of bug 222397
Product: evolution
Classification: Applications
Component: Calendar
2.26.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-05-01 21:36 UTC by Severo Raz
Modified: 2012-04-20 12:05 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Severo Raz 2009-05-01 21:36:11 UTC
In this bug report, or feature request, I will post two things that I think will improve a lot the Evolution calendar.

My first point is that todos, as any other task or event, should be able to have a place in the calendar. This way, todos can graphically represent their due date. Plus, TODOs in the TODO view should have a progress bar to, again, graphically show the progress of the task.

The second idea I want to introduce is that the calendar should be more legible. With more legible I mean that it should have more space to be read. Therefore, the calendar should have an option in the Evolution preferences to show only the calendar when in month mode, hiding the tasks bar and todo bar.
Comment 1 André Klapper 2009-05-03 17:13:22 UTC
Please post only one proposal per bug report and use a meaningful summary, otherwise it is impossible to handle this correctly.
Comment 2 André Klapper 2012-02-13 15:42:20 UTC
Re-reading this I don't understand the requests - what is a "TODO" exactly? A memo? A task? In the second part, I don't understand this sentence:

> The calendar should have an option to show only the calendar when in 
> month mode, hiding the tasks bar and todo bar.

Could you please clarify?
Comment 3 Matthew Barnes 2012-02-13 17:54:52 UTC
(In reply to comment #0)
> Therefore, the calendar should have an option in the Evolution preferences to
> show only the calendar when in month mode, hiding the tasks bar and todo bar.

We already have this, no need for a preference.  The pane divider separating the calendar and the task/memo lists is tracked separately for month view.  So just drag the divider all the way to the right and the task/memo lists will stay hidden in month view without affecting the other views.
Comment 4 Severo Raz 2012-02-13 18:31:04 UTC
(In reply to comment #2)
> Re-reading this I don't understand the requests - what is a "TODO" exactly? A
> memo? A task? In the second part, I don't understand this sentence:
> 
> > The calendar should have an option to show only the calendar when in 
> > month mode, hiding the tasks bar and todo bar.
> 
> Could you please clarify?

Yes of course, sorry talking about the TODOS, I can't find them and can't figure out where did I get them from when I was writing that. I also apologize for my so late response. 

What I meant was that tasks should have a place in the calendar. They should appear as an event in the calendar in the day they are due.
Comment 5 Severo Raz 2012-02-13 18:31:26 UTC
(In reply to comment #3)
> (In reply to comment #0)
> > Therefore, the calendar should have an option in the Evolution preferences to
> > show only the calendar when in month mode, hiding the tasks bar and todo bar.
> 
> We already have this, no need for a preference.  The pane divider separating
> the calendar and the task/memo lists is tracked separately for month view.  So
> just drag the divider all the way to the right and the task/memo lists will
> stay hidden in month view without affecting the other views.

That is very good to know :)
Comment 6 André Klapper 2012-04-20 12:05:00 UTC
(In reply to comment #4)
> What I meant was that tasks should have a place in the calendar. They should
> appear as an event in the calendar in the day they are due.

Marking as duplicate.

*** This bug has been marked as a duplicate of bug 222397 ***