Closed
Bug 436636
Opened 14 years ago
Closed 14 years ago
implement way to queue and display notifications
Categories
(Cloud Services :: General, defect, P1)
Cloud Services
General
Tracking
(Not tracked)
RESOLVED
FIXED
0.2
People
(Reporter: myk, Assigned: myk)
References
Details
Attachments
(3 files, 5 obsolete files)
109.30 KB,
application/pdf
|
Details | |
17.51 KB,
image/png
|
Details | |
42.28 KB,
patch
|
Details | Diff | Splinter Review |
There should be a way for Weave to queue up notifications for the user as it generates them and then display them for the user when the user wants to see them. Here's the beginnings of such a beast, a work in progress that reuses some Firefox notification XBL. It doesn't work yet.
Comment 1•14 years ago
|
||
Cc'ing Mano, he's working on this.
Assignee | ||
Comment 2•14 years ago
|
||
Here's a mockup from Maria of what we're looking for in the notification UI. The one element of this mockup that needs to be changed is the depiction of a notification with an action needed. The mockup depicts the action the user can take as a link, but some such notifications will have multiple choices, and some will require additional UI elements like a list of checkboxes. For example, the notification that "someone wants to share a bookmark folder with you" should let the user say "Yes" or "No" to the request. And the notification that there are "Tabs From Other Computers" will have a list of tabs the user can open, with checkboxes for choosing which ones to open. So instead of links, the actions should be buttons.
Assignee | ||
Comment 3•14 years ago
|
||
Here's what the tabs notification looks like currently, so you can see an example of the kind of "action needed" notification that will be integrated into the notification system. Besides folder sharing and tabs notifications, the other major notification that will require an action is when login or syncing fails for some reason. There we might allow the user to "Verify Username/Password" or "Try Again" or the like.
Comment 4•14 years ago
|
||
mano, are you working on this? any progress? trying to get a feel for if we'll be ready for a some test builds over the next day or two
Updated•14 years ago
|
Severity: normal → blocker
Assignee | ||
Comment 6•14 years ago
|
||
Attachment #323188 -
Attachment is obsolete: true
Assignee | ||
Comment 7•14 years ago
|
||
This is close, but it isn't quite there yet. There are positioning and style issues (icon should be next to weave username, panel should open in corner of browser, warnings and errors should have correct icons and background colors), and it should be possible to add buttons using the basic notification. But adding and removing notifications works, and tab notifications are now integrated into this consolidated notification UI, providing an example of how you can create a custom notification that does more than the basic notification provides. I'll try to finish this up tonight.
Attachment #326421 -
Attachment is obsolete: true
Assignee | ||
Comment 8•14 years ago
|
||
Here's a working version, modulo some bugs and a variety of appearance/behavior issues. I'll wait to check this in until tomorrow, when I can run more comprehensive tests and document the issues encountered (and also how to add a notification).
Attachment #326597 -
Attachment is obsolete: true
Assignee | ||
Comment 9•14 years ago
|
||
The previous patch was missing some files. This patch contains them.
Attachment #326672 -
Attachment is obsolete: true
Assignee | ||
Comment 10•14 years ago
|
||
This patch fixes various bugs in the previous one. Other bugs remain, and there's lots of polish work to do, but that's all best worked on with this patch in the tree, so I'll push it shortly.
Attachment #326674 -
Attachment is obsolete: true
Assignee | ||
Comment 11•14 years ago
|
||
changeset: 729:10512274ea50 tag: tip date: Wed Jun 25 13:51:39 2008 -0700 summary: bug 436636: a system for showing various kinds of notifications in one consolidated location
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Component: Weave → General
Product: Mozilla Labs → Weave
Updated•13 years ago
|
QA Contact: weave → general
You need to log in
before you can comment on or make changes to this bug.
Description
•