Multiple Calendars with Print Capability

RESOLVED WORKSFORME

Status

Calendar
General
--
enhancement
RESOLVED WORKSFORME
11 years ago
11 years ago

People

(Reporter: Robert, Unassigned)

Tracking

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
Build Identifier: Sunbird 0.5 and Lightning 0.5

Being able to manage and view multiple calendars is a useful feature in Microsoft's Outlook, but it doesn't allow for printing of multiple calendars at the same time.  Where I last worked it was necessary for us to put calendars from 4 people on the same sheet for the boss, but it took a lot of effort to do that simple task.  Microsoft has not yet figured out how useful that feature can be or has not programmed it in.  This feature would put Mozilla in a major position to oppose Microsoft's dominance in that market.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
I don't get the point. You can already view, manage and print multiple calendars in Sunbird/Lightning. You can print them all in one or one by one if you like.
Whiteboard: [qa discussion needed]

Comment 2

11 years ago
Yes, existing feature, marking WFM.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
Whiteboard: [qa discussion needed]

Comment 3

11 years ago
Hi,

My problem with printing multiple calendars is how do you know which one is which. In Week & Month view there each entry is colour coded, but this will be specific to whoever printed the calendar. If you use the list view this feature isn't there. Either the event header needs the calendar name (or an option to show it, at least), or the colour code key needs to be printed as well. For this last option to work, the list view will need colour as well. It may also be necessary to prevent two identical colours being used for different calendars as this would break the key.
Marco, please file a separate enhancement request for your problem.
You need to log in before you can comment on or make changes to this bug.