Closed Bug 498366 Opened 15 years ago Closed 11 years ago

When installing Growl, it should work without having to restart the application

Categories

(Toolkit :: UI Widgets, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: florian, Assigned: florian)

Details

Attachments

(1 file, 1 obsolete file)

Attached patch Patch v1 (obsolete) — Splinter Review
Currently, Growl is registred after the final-ui-startup notification. If it is installed on the system after the XUL application started, it won't be usable until a restart of the application.

The attached patch changes the code to register with Growl after final-ui-startup if Growl is installed, or at the first ShowAlertNotification call after the installation of Growl.

Note: Without the patch, debug builds crash at the first ShowAlertNotification call after the installation of Growl on this line because mDeletage is NULL:
  NS_ASSERTION(mDelegate->delegate == [GrowlApplicationBridge growlDelegate],
Attachment #383283 - Flags: review?(mano)
What's the reason not to launch growl only in  ShowAlertNotification?
Attached patch Patch v2Splinter Review
(In reply to comment #1)
> What's the reason not to launch growl only in  ShowAlertNotification?

I didn't want to change when the before-growl-registration notification was sent in the common case of Growl already installed before the XUL application starting. Looking at it again, I'm not sure it made sense...

With this version of the patch, I'm not sure the Init method is still useful. I tend to think it's better to fail and produce a JS error on the getService call rather than on the showAlertNotification call, but I guess that's debatable.

It would also be nice to add there a clear error message reported to the error console, in addition of the NS_ERROR_SERVICE_NOT_AVAILABLE result code. That's probably covered by bug 382715 though.
Attachment #383283 - Attachment is obsolete: true
Attachment #383358 - Flags: review?(mano)
Attachment #383283 - Flags: review?(mano)
This breaks the user experience that mac users would expect.  All applications that use Growl register at application startup.  This is especially obvious the first time an application runs because growl will notify the user that the application has registered with Growl.

How do other applications on the mac (like Adium) handle the case of Growl being installed after the application is running?
Comment on attachment 383358 [details] [diff] [review]
Patch v2

I don't use growl much, so someone else should figure out what's the right UE. Then, please ask for review again.
Attachment #383358 - Flags: review?(mano)
Bug 782211 removed growl support.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: