On Wednesday, July 18, 2012 at 12:44 PM, Josh wrote:
> > On 18 Jul 2012, at 17:54, WesTurner wrote: > > > Hello all, > > > > #1: > > I've bought the growl 1.4 from the app store. The transition was a bit of a > > pain. Here's to hoping the growl team can work on proper clean-up scripts. > > It seems that when I paid for, downloaded, and installed the latest growl > > application from the app store, it was ignorant to the older version, which > > caused conflicts. On a reboot, even after using the uninstall script, the > > old preference pane was still present and the app store had growl marked > > for an update. Is there something preventing the install process from > > performing this maintenance clean-up on its own? If so, that is > > unfortunate. It seems un-mac to have to delve into uninstall scripts to > > upgrade to the latest version. Reminds me of MS office and adobe installs. > > > > > It is unfortunately (I believe) a bug in the app store. If you haven't > already, grab a copy of the uninstaller for 1.2 from > http://growl.info/downloads and remove the old pref pane completely along > with the new Growl.app, then download from the app store fresh. > So what happens is that the app store updates by bundle identifier, and that's how Growl from the app store ends up inside the prefpane. The reason for this on their end is that an application can be moved around the file system. So for instance if you moved iPhoto, in theory updating the application associated with the iPhoto bundle identifier would be appropriate. For Growl this becomes a slight issue, as you have seen. If you do not remove Growl from the system as we recommend here http://growl.info/growlupdateavailable then you may end up with what was on the app store inside of Growl.prefpane, replacing GrowlHelperApp.app. There is no solution to this like you want unfortunately. We've added something in Growl 1.4 that should detect this situation though, and then sends you to http://growl.info/growlinstallcorrupt . We don't have a better solution for this, and likely never will. > > > > #2: > > Also, after reading this page, it states that growl doesn't need to be > > installed in order for growl to work? How does this work? I've already > > installed it, so it's a moot point, but I would like to know. How would one > > enable growl notifications and furthermore, disable and configure certain > > apps, on Lion if they don't download the growl app? Is configuration then > > left to the apps that have these notifications itself? and the growl app is > > then an override for themes,etc? > > > > > Applications using the new Growl framework have bundled in this framework a > thing called Mist which is like a Growl lite. Basically the framework looks > for Growl, and if it finds it, sends Growl notifications as usual. However, > if it doesn't it uses this built-in notification system instead, which > displays growl-like notifications but with no customisation and other useful > bits available like you get with Growl. > If you want to see what it looks like, find an app that makes use of the new > framework (for instance Adium), quit Growl, and generate a notification; it > will use Mist instead. > > > -- > 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] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. > > -- 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.
