This is bad. If something happens to have the name Growl in it but
isn't related to our project, then that gets quit too. I'd rather have
less quit that left stuff running related to Growl than have more quit
that led to potential data loss.
I'm not opposed to trying to make something work though that covers
everything, but I don't know if it's expected behavior to quit a bunch
of apps if it's just Growl that you're uninstalling.
Chris
On Oct 11, 2009, at 6:25 PM, Deivy Petrescu wrote:
>
> Hello all,
>
> It's been a while since I wanted to suggest that, but I keep
> forgetting.
> The uninstall script that comes with the Growl install package does
> not do a good job quitting apps.
> If one wants to quit Growl, it should also quit all the "peripheral"
> apps, like Hardware Growler, for instance.
> So, if you do not mind i suggest the following script instead:
> <script>
> display dialog (localized string "title")
> if button returned of result = "OK" then
> tell application "System Events" to set l to get name of every
> process whose name contains "Growl"
> repeat with ll in l
> set ll to contents of ll
> tell application ll to quit
> end repeat
> do shell script "rm -rf /Library/PreferencePanes/Growl.prefPane ~/
> Library/PreferencePanes/Growl.prefPane" with administrator privileges
> display dialog (localized string "succeeded") buttons {localized
> string "OK"} default button 1
> end if
> </script>
>
> This way, every single process that depends on Growl is quit as well.
> Then, just install the new version.
>
>
>
> Deivy Petrescu
> [email protected]
>
>
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
