Closed Bug 449224 Opened 16 years ago Closed 11 years ago

Enable notification panel for QAC

Categories

(Other Applications Graveyard :: QA Companion, defect, P2)

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: coop, Unassigned)

Details

Attachments

(1 file, 2 obsolete files)

As discussed at the Summit, it would be very useful to get the code in place for the popup notification panel in the QAC (similar to the popup in the joga extension). This would allow us to use the tool for one of its original intended uses, i.e. pushing information about upcoming testdays and bugdays directly to interested parties.

Assigning directly to Zach since he voluteered to take this on at the Summit.

Zach: let me know if I need to do any work Litmus-side to help with this.

cc-ing Tomcat because I mentioned adding this to his workflow for testday/bugday notifications, since he currently sends out those weekly emails. However, I also now think that we could generate these updates automatically from the Litmus database (for testdays at least), provided someone sets up the appropriate testday in Litmus first.
Priority: -- → P2
As far as I know, no one is working on this, resetting assignee
Assignee: zach → nobody
Attached patch basic patch (obsolete) — Splinter Review
This is a initial patch for the notification system. It's pretty basic, it just checks the QMO events feed for new items every 30 minutes and displays the notification panel with the event information if there is a new event. 

The final implementation isn't going to look much like this. As Clint and I discussed on irc, we're going to go for a system where we check multiple feeds on QMO (events, forums, news) and in some situations store the feed item for deferred display. This patch is more to get a feel for a possible UI. There are comments in chrome/content/notification.js where you can change the interval for checking the feed and display timing.

is this the right bug?
Assignee: nobody → harthur
(In reply to comment #2)
From a quick overview of the patch, it looks like the right approach.  One thing I started thinking about after downloading the latest Shredder (which uses the standard OS notification system, pop-ups from toolbar on windows, growl on OSX probably something else nifty on linux...is whether or not QAC should do the same.  Coop - was there any reason why your original intention was an entirely in-browser notification system?  If the user is already accustomed to configuring and seeing notification systems with method X then it seems we should also use method X.  I'll take your patch and install it in my minefield and get an idea of how it feels to see the notifications pop up.
> is this the right bug?
Most assuredly yes, yes it is. :-)
Attached patch patch v0.1 (obsolete) — Splinter Review
This patch looks a lot more like what the end implementation will be. This checks the three QMO feeds (main blog, events, forum) every hour and stores the title of the feed item and the link to more information in a database. Every so often, QAC checks the database for anything that needs displaying and pops open a panel right above the QAC icon on the statusbar. Right now every item is displayed as soon as the QAC sees it, but it the future, we could have items published to the feed with a set "time to display", which is the reason for the database. There are a couple edge issues this patch doesn't address right now:
1) multiple windows, right now we are checking the feeds/database via a setInterval on every browser window. 
2) user changing checking interval preference in the middle of browsing session 3) disabling all notifications.

I'm working on a patch for these issues and also an alternate UI for displaying in the system tray instead of in-browser. But try this one out to get a feel for the UI, content and timing. To really test the UI, you can uncommment the line I've marked with "UNCOMMENT HERE" in notification.js and this will display every notification from the past three days every hour, otherwise, you will only see each notification once and this could happen only a couple times a day.
Attachment #364239 - Attachment is obsolete: true
Attached patch patch v0.1.1Splinter Review
apologies, the last patch had a stray catch statement I forgot to remove.
Attachment #371939 - Attachment is obsolete: true
Assignee: fayearthur → nobody
Litmus has been replaced by MozTrap. 

If we want an extension to integrate with MozTrap, it would be better to start from scratch with a new extension rather than trying to shoehorn that functionality into the >5 year old QAC.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.