Open
Bug 412803
Opened 17 years ago
Updated 2 years ago
Add selector of writeable calendars to the "click here to create a task" line
Categories
(Calendar :: Calendar Frontend, enhancement)
Calendar
Calendar Frontend
Tracking
(Not tracked)
NEW
People
(Reporter: davida, Unassigned)
References
Details
(Whiteboard: [has l10n impact])
I really like the idea of the 'click here to create a new task'. One quibble -- I find that it's easy to create a task in the wrong calendar, because the notion of selected calendar is fairly fair away (visually) from the task entry line.
One possible way of addressing this is to add a dropdown menu to the right of the textbox (which is quite long anyway), indicating the current calendar (with the color vignette for quick checking), as well as affording a choice of selecting any other read-write calendar (no read-only calendars should be in this dropdown).
Christian, your thoughts?
Comment 1•17 years ago
|
||
This would be one possibility. I find it hard to do this in a space-saving manner though. While its probably not bad for the task view, the task quickadd feature in the today pane is a bit harder to take care of.
We have bug 366914 to find a way to make the default more obvious.
Comment 2•17 years ago
|
||
How about adding the selected calendar name to the help text itself? Like 'click here to create a new task in calendar Home'.
Comment 3•17 years ago
|
||
I think a drop down like the TB search bar provides would be sufficient.
[ ICON \/ Click to Create Task ]
| Home |
| Cal 2 |
| ... |
+-------+
Reporter | ||
Comment 4•17 years ago
|
||
Agree w/ comment #3, especially if the icon has the color of the relevant calendar.
The drop down list should display writeable and task-enabled calendars only, and automatically select the unique one in case there is only one calendar that fulfill the criteria.
Updated•15 years ago
|
Assignee: chris.j.bugzilla → nobody
OS: Mac OS X → All
Hardware: x86 → All
(Sorry for the faulty commit).
I strongly propose to add this feature. When you enter a new task while using Google Calendar per CALDAV (which cannot maintain tasks) an error message appears and the newly entered task is lost. This is quite annoying and makes the "Quick-Entry"-field unusable. (Might even qualify as a bug.
Updated•15 years ago
|
Flags: blocking-calendar1.0+
Whiteboard: [not needed beta][has l10n impact]
Comment 10•14 years ago
|
||
This has bitten me before, so I'm taking it. I have a patch in progress that I should be able to upload in a few days.
Assignee: nobody → squibblyflabbetydoo
Status: NEW → ASSIGNED
Comment 11•14 years ago
|
||
I think this is already fixed. At least for Google Calendar it says in the Quickentry textfield: "Bitte einen Kalender auswählen, der Aufgaben unterstützt" (Please select a calendar that supports tasks).
Don't know if there are other issues related with this but for me this is sufficient.
Comment 12•14 years ago
|
||
The error message is fine, but as the original description of this task states, the interface for selecting a different calendar is too far away (potentially not even on the screen, if using the Today Pane).
It took me some time, as a user, to understand that a global "selected calendar" even existed; a local "which calendar you're creating a task in" drop-down would make much more sense.
Comment 13•13 years ago
|
||
Jim, any updates on this bug?
I'm going to take this off the blocking list because if we fix this in one place (i.e the task selector), then we should be consequent and find a solution for all areas.
Flags: blocking-calendar1.0+ → wanted-calendar1.0+
Whiteboard: [not needed beta][has l10n impact] → [has l10n impact]
Comment 14•13 years ago
|
||
I've got a patch in my queue that I never quite finished the styling for, so it currently looks bad but works. I'll take a look at it again, hopefully in the near future (my Thunderbird patch queue is pretty big though).
Comment 15•11 years ago
|
||
I'm unlikely to work on this any time soon. Sorry!
Assignee: squibblyflabbetydoo → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•