Framework-only Growl should have ability to be globally disabled

[GoogleCodeExporter]

Some users keep Growl uninstalled on their system because they do not want to 
see Growl notifications. If an application is using the Growl framework to 
display notifications, it would be required to add a preference for, "[√] 
Display notifications using Growl" (or the like) which is more or less against 
the spirit of configuring applications inside Growl themselves.

Since every app having a preference for whether or not to display notifications 
could be cumbersome, and since the 1.3 framework will display notifications on 
its own if Growl is not installed, some kind of global preference (`defaults 
write`) should be checked before doing any display. Additionally, a helper .app 
may be useful to distribute on the Growl website with a global on/off switch 
for whether or not notifications are displayed.

Original issue reported on code.google.com by zacw...@gmail.com on 4 Oct 2011 at 1:16

[GoogleCodeExporter]

Moving these to 1.3.2 so that we can address issues brought up right after 1.3 
came out.

Original comment by ch...@growl.info on 5 Oct 2011 at 12:21

• Added labels: Milestone-1.3.2, Product-Growl

[GoogleCodeExporter]

I have added a disable default, com.growl.growlframework.mist.enabled
If the key isn't present, Mist defaults to on.  If present and false (0), Mist 
is disabled.
This works according to standard NSUserDefaults rules, and I have tested it as 
a global off switch in a sandboxed app

Original comment by dan...@growl.info on 10 Oct 2011 at 4:26

• Changed state: FixedInSource