On May 19, 8:54 am, Derik DeLong <[email protected]> wrote: > Not that I should butt in, but I don't see the point of disallowing > users from using Growl with applications other than the whitelisted > applications. I could understand an admin wanting a white list that > limits the number of Growl alerts, reducing user tickets. > > However, if a Growl supporting application is installed in the system > (which I would expect would require administrator access to install in > the first place), what's the reasoning behind restricting a user from > viewing its Growl alerts?
Like I said, it doesn't really matter because with the whitelist in place, if an admin wants to block access to Growl entirely but maintain the white listed alerts, it's just a matter of blocking access to the Growl Preference Pane, which is trivial and takes the burden off of the Developers, leaving it up to the admin to decide whether they want the user to be able to configure more Growl settings. So no, I don't disagree with you Derik. However, I would advocate that the whitelist allow for setting the alert style and stickiness so that if the admin does decide to block access to the Growl System Preference Pane they can also ensure that the alerts are consistent from user to user (or that they can change the style or stickiness centrally without having to touch each machine). As far as apps that support Growl being installed by an admin - let's just say that some apps support Growl alerts in a meaningful way, others in an annoying and distracting way (this is all subjective of course). All it takes is one essential app with a poor Growl implementation (Adobe) and therefore it's easy to turn thumbs down on Growl as a whole. For example, there's some apps that will literally fill your screen with sticky Growl alerts of a repeated message. Bad behavior. As an admin, I'd like to keep that app, but manage its ability to use Growl. If the app were essential, and I had to choose between it and Growl, I'd probably choose the app. That's the whole point of this discussion / feature request- not to have Growl fall victim to one vendor or programmer's poor use of it. The information it would publish via Growl > is just accessible within the application itself, so the only thing > you'd accomplish is making it harder for users to be informed about > data they already have access to. > > Unless I'm missing something. (This is all from the perspective of > someone who regularly works in managed environments.) > > On Wed, May 19, 2010 at 3:59 AM, Peter Hosey <[email protected]> wrote: > > On May 18, 2010, at 21:22:20, Chris Forsythe wrote: > >> This overrides one of our main goals, giving users the control. I'm ok > >> with a white list, but the end user must have control. > > > I think the rules are different in a managed environment. It's not the > > user's computer, it's (effectively) the admin's, so it's the admin who > > should have control. > > > The user needs to have *some* control, such as the ability to disable > > certain notifications and to customize their display to their taste, but > > when there is an admin, the admin should have the power to set whatever > > limits they see fit, including an exclusive list of applications allowed to > > post Growl notifications. Allowing the user to override such a list > > undermines that power. > > > So, I think Growl should simply obey the whitelist, at least when it is > > enforced, and display (one way or another) that there is one. > > -- > 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 > athttp://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.
