On Mon, May 17, 2010 at 4:40 PM, sourcehound <[email protected]> wrote:
> > > On May 17, 2:53 pm, Christopher Forsythe <[email protected]> wrote: > > Ya, I saw that thread. I almost joined, but didn't at the last minute. > > > > Whether an application notifies is stored within the <users>/Application > > Support/Growl directory I believe, not in Preferences. The link you > provided > > didn't work for me, or I'd have dug into what this is exactly. > > > > We're not opposed to admins trying to run their network. And > unfortunately > > we're stuck in a boat you guys are, in that adobe is installing this and > > there's no control here. We'll do what we can to help here. > > > > Right now I'm trying to gauge how long it will take to get sparkle > > integrated into Growl, so that we can at least provide better updating > > mechanisms on the *next* update. However we have some pretty important > fixes > > to go out, so if it takes too long, we'll probably push 1.2.1 and update > > version checking in 1.3. And then get slammed with "hey, what's growl" > > questions from people who shouldn't have to ask them > > > > Can you find the correct link to that document? > > > > Chris > > > > > > > > On Mon, May 17, 2010 at 1:57 PM, sourcehound <[email protected]> > wrote: > > > Recently, there was some discussion on the Mac Enterprise list > > > ([email protected])of how Adobe snuck a Growl Install in as > > > part of its own installation registration process, then failed to > > > clean it up. During the discussion, some network managers expressed a > > > dislike for, or discomfort with Growl. I do not share that dislike or > > > discomfort, though I do understand why they might feel that way. > > > > > While the Growl Application Framework is a nice step away from a > > > system-wide Growl for some developers, those of us who are System > > > Managers would probably appreciate a way to manage Growl alerts for > > > individual apps using an MCX Preference Manifest that could be used > > > for Group Policy enforcement. That way, if a System Manager decided > > > one app needed to use Growl, but didn't want Growl alerts for other > > > apps, these settings could be managed using centrally. > > > > > Here's a PDF from Apple about Preference Manifests. > > > > > developer.apple.com/.../Preference_Manifest.../ > > > Preference_Manifest_Files.pdf > > > > > Thoughts? > > > > Chris, > > if you are going to implement Sparkle, you might find that some > Network Managers sort of hate that too. At the very least, provide > some mechanism so that the SU check on startup can be disabled - hey, > like a preference manifest. > > Basically, Network Manager want to be able to control all aspects of a > program's behavior. Adding Sparkle to Growl will just make many > dislike Growl more as that's just more uncontrolled prompts they can't > manage. The solution = keep Growl off their machines. > > See where I'm going with this? > > Since "check for updates" would be in the preferences file, that should be taken care of pretty easily right? I think you misread things here. Nobody is dismissing things automatically, Peter and I are both just talking about the technical aspects within Growl. That said, I don't think Growl fits entirely with the network manager view. Growl is so that the *user* can control what notifications they get. If the user isn't able to control that, it's annoying. -- 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.
