On Nov 8, 4:16 pm, Travis Tilley <[email protected]> wrote: > A number of applications (including last.fm for example) didn't use the > public API to check whether or not growl was running or installed. Many of > them implemented their own checks in a variety of ways... from checking > file locations to seeing if there's a process with the name > 'GrowlHelperApp' (which is now just 'Growl' due to the change to being an > app). The latter is unexpectedly common (I believe super duper is/was doing > something similar?).
I agree that app developers that use private, unstable interfaces are making a mistake that is likely to hurt their customers in the long run. > To complicate matters further, there was at one time a bundle framework > that included an installer to auto-install growl if it was missing. Due to > abuse and complaint, this version of the framework was abandoned. There is > no recent framework+installer, and simply dropping the standard growl > framework in its place will not work. That's not what I just discovered for the Google+Growl plugin. See my other recent post for details. Beyond this, dropping the framework +installer and not providing an automatic upgrade path to people that install Growl 1.3 for older apps that are using the framework +installer legitimately (i.e. calling the public APIs) is on the Growl developers. -- 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.
