On Aug 30, 2011, at 10:24 AM, Phat Bob wrote: > > > On 29 Aug 2011, at 20:44, Chris Forsythe <[email protected]> wrote: > >> >> On Aug 29, 2011, at 2:09 PM, SteveCronin wrote: >> >>> To be clear, you cannot specify which notification display to be used >>> unless you manipulate preferences. If you are a system administrator >>> over 5000 machines at a college, then that *might* be appropriate. As >>> an application developer though, that is very inappropriate. >>>>> That is, will my 'branding' survive regardless of the user's preferences? >>>>> Does this include like starting position? >>>> Applications can't set the starting position, or any other display >>>> settings. >>> Why do you want/need this? >>> >>> Are you saying tha when 1.3 ships - if I install the Growl framework >>> 'privately' that I cannot control the appearance of my notifications? >> >> You cannot control it regardless of the version. Your own predilection for >> whatever product you produce does not mean that the user wants to see a >> giant pepsi logo on their screen for every notification. >> >> >> The 1.3 framework will not install Growl, at all. The 1.2.2 with-installer >> framework will install Growl, but only if the end user chooses to do so. You >> cannot depend on it being there in 1.2.2. 1.3 will have a very limited >> capability notification built into the framework. >> >>> Branding and consistency are critically important characteristics of a >>> notification that we would want to serve. >> >> Why? Every notification shows the application or a different image in the >> notification, why would it matter which display the end user chooses to use? >> This is important for us, for any app dev who has brought this up before >> once we start talking about this they say that this behavior works for them. >> So if it does not work for you, we need to know why. > > I've been following this thread as this is what I've been trying to achieve > but on Windows. > > I manage a call centre of 2,500 staff and needed a notification system > whereby users are subscribed to notifcations sent from a central server and > also receive notifications from a .net app we run. > > Our users are not "users" as the Growl team sees them; instead they're > employees of a company and therefore we want a consistent branding and > appearance in the same way as we prevent the CC staff changing their desktop > wallpaper and screensaver. > > We have regular visits from media and other third parities and therefore not > allowing our users the ability to "fiddle" with settings is crucial from a > company reputation perspective and from an IT support perspective as well. > > We've since solved the issue using a Windows product similar to (but not) > Growl for Windows. > > I'm only posting here as it might help Chris and Peter understand the OP's > requirement better.
Right, and to me that's a good situation that overrides things, unless the end user understands what the notification system actually is. I do not believe that this is the case for the original poster. I believe he is creating an application. I could always be wrong here, but let's wait and let him answer that for us. Chris > >> >>> Let's pretend: I'm Apple (or Pepsi, or Nike, or Starbucks, or ..)if >>> I want to serve up a custom notification and I have installed Growl >>> 'privately' for this >> >> Define "privately" please. >> >>> - then I don't want the user's predilections for >>> satanism, soft-core, whatever, hijacking my message… >> >> The user can install whatever display style that they want, but they have to >> install it. >> >>> So, in 1.3, here's what I think you said: >>> 1) will be able to install 'privately' BUT >> >> It will not install Growl at all. >> >>> 2) no developer control over notification characteristics >>> So all of the methods in GrowlSamplePrefs.h will disappear? >>> >> >> Developers do not control the look and feel of a notification regardless of >> version of Growl. The core design of Growl is that the end user ultimately >> decides what Growl looks and feels like. Their "predilection" is what >> matters. If a user doesn't like to see a pepsi symbol every time they get a >> notification about a new email from apple mail, they simply should not have >> to. Thinking about the end user is our goal, it should be yours too. >> >>> When 1.3 ships does this mean if I install my application on a Mac >>> that already has Growl installed then, using the new 1.3 Cocoa API, I >>> cannot present notifications to the user which comply with my 'brand- >>> approved' settings? >> >> Please explain "brand-approved" settings. Are you planning to spam users >> through Growl or what? What we do with Growl is give the end user what they >> want with notifications, i.e. the last line of control. I'm confused as to >> why your company/managers wouldn't want this as well, but I need more >> explanation as to exactly what you are planning to do in order to help >> answer your question. >> >> Do you have mockups of what your company wants to do? That might help >> immensely. >> >> >>> >>>>> 3) Is there a way to make an application NOT appear in the 'Applications' >>>>> list in Growl's user preferences? >>>> No. >>>> User control—including the ability to override settings provided by >>>> default by applications—is a central Growl design principle. >>> Why do you want/need this? >>> >>> --- Wanted to have a 'hard' answer for the horse's mouth. So this >>> represents the user's 'opt-out' mechanism for any application's Growl >>> behavior, yes? >>> >> >> I don't understand the part about "horse's mouth". Applications do not >> control Growl at all. They simply send a registration to Growl, and then >> notification strings and icons, that's it. That is the end of the >> responsibilities for applications talking to Growl. Users control the look >> and feel of Growl. We try to default to a nice looking display, but users >> can have Growl display it differently, or even just email it or send it to >> their mobile device. >> >> >> Maybe this would be better if you were to explain exactly what your >> requirements are here. We're talking all pie in the sky right now, and >> trying to explain how Growl works, but it may be more helpful if you just >> gave us your list of requirements than anything else. Being on the same page >> would probably help communication immensely. >> >> 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. >>> >> >> -- >> 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. >> > > -- > 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. > -- 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.
