On 18 May 2010, at 03:28, Peter Hosey wrote: > On May 17, 2010, at 16:32:50, sourcehound wrote: >> There's a school that says "a silent system is the best system." However, >> some admins would want to allow Cyberduck to use Growl notifications, but >> might want to disallow Mail.app from using Growl notifications. > > The existing solution to that specific example would be to simply not install > GrowlMail. ☺ > >> A simple whitelist approach limits the notifications to "blessed" apps. > > Sounds good. Here's my proposal: > > A preference, named in the manifest, whose value (if set) is an array of > application names. If this preference is set, it is a white list; Growl will > accept registrations from other applications but ignore their notifications. > It should also show other applications' names in strike-through type in the > preference pane. >
I haven’t completely thought this through, particularly with regard to existing installations & registrations (perhaps another pref var ‘resetToWhiteList’ or something), but possibly the aforementioned whitelist could merely denote that all new app registrations apart from those listed default to having their notifications disabled (i.e. when writing the new growlTicket, all notifications have enabled unchecked)? Then users like me who don’t like to be told how to use their computer by their admin still have full control over their notifications (provided they can reach the prefpane/know how to dive into the ticket). -- 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.
