On Tue, May 18, 2010 at 9:15 AM, Evan Schoenberg, M.D. <[email protected]>wrote:
> > On May 18, 2010, at 9:04 AM, Christopher Forsythe wrote: > > > I think we should maintain this, and can maintain it, while adding the > white list feature. > > > > What I think we should do is have the strike through like Peter mentions, > and the white list. Add in the "ignore my admin" hidden default, and I think > that solves the problem i.atent.dead has. > > > > The only other thing we need to do is make sure it's apparent that this > is what's happening, so that the user knows what is going on, if they are > like i.atent.dead. > > > > I don't like the disable everything on registration, because then it's a > lot of work to get it back to how users like things, if they know enough to > know they want to enable it all. It'd be easier for them to get going with a > quick defaults command. > > Does this need to be hidden? Is it possible for Growl to know that it's > being overridden at an administrator level? If so, could we just reveal a > checkbox, or popup a window when the Growl preferences open, giving the > opportunity to override that? > > That's a good point. No, not hidden. I just didn't want people who aren't under this restriction to have to see this checkbox and then ping us asking what it was. Magical unhiding preference is a great idea. How much work does this white list, strike through, and this disappearing/reappearing preference take to accomplish? Chris -- 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.
