On Oct 5, 2011, at 03:19:44, howzitgoan wrote: > Growl 1.3 has no "GrowlHelperApp", therefore apps that depend on it, or > expect it, crash. For example, Calibre (latest version) pops up a "Where is > GrowlHelperApp?" window with a list of applications, then promptly crashes. > > Maybe this is a Calibre bug, but if so why has the registration process > changed so radically?
Growl 1.3 is intentionally a descendant of GrowlHelperApp, with the same bundle identifier, and one reason for this was compatibility with existing AppleScript scripts. The AppleScript interface, at least when I was involved in the project, was only intended for users' own scripts. Applications were/are supposed to use the Growl framework, not AppleScript, to talk to Growl. The framework interface remains intact for now, and 1.3 adds a new one that will eventually replace the old one (but not yet). (In case anyone is curious: The 1.2.2 framework only supports the old interface, so switching to it is a short-term fix. As soon as framework 1.3 comes out, applications should switch to that, as it supports the new GNTP interface.) The specific problem you're having is either a Calibre bug or a Mac OS X bug. The larger problem is that Calibre is an application talking to Growl over AppleScript; they would probably be better served by either switching to the Growl framework (I'm not sure what Calibre is written in, so I'm not sure how feasible this is) or using a GNTP library. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
