On 8/4/13 2:33 PM +0900, Philip Chee wrote:
I haven't looked into this in detail but in principle you could implement your own nsIAlertsService in javascript and make yours override the built in service.
Hmmmmm. That's an interesting idea. It seems a bit more complex than I'd hoped, though, because the extension itself would need to be in charge of any audio notifications. This particular extension uses growlnotify (a CLI tool) to talk with Growl. As such, it's a one-trick pony in terms of audio notifications: You can either get no audio notifications from the extension or you can get audio for all notifications. In that sense, this extension is a large step backward from the built-in Growl support that SeaMonkey used to have, as SM could be specific about what notification it was giving to Growl. That granularity would likely need to be coded into the extension itself now.
http://mxr.mozilla.org/comm-central/source/mozilla/toolkit/components/alerts/nsIAlertsService.idl http://mxr.mozilla.org/comm-central/source/mozilla/toolkit/components/alerts/nsXULAlerts.cpp You might want to read this change set to get a bit of background: http://hg.mozilla.org/mozilla-central/rev/d068e438438d https://hg.mozilla.org/mozilla-central/rev/c9732200552d And the other patches in Bug 782211 <https://bugzilla.mozilla.org/show_bug.cgi?id=782211>
Many, many thanks, Phil. I'll have a good look at these. I'm also going to look for/at the Growl tidbits from the 2.17.1 source and compare it to the original circa-2007 FF extension that introduced Growl to the projects. We'll see how it goes.
Cheers, trane -- ///////////////////////////////////////////////////////// // Trane Francks [email protected] Tokyo, Japan // Practice random kindness and senseless acts of beauty. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
