Dear Peter and others, Thank you for taking the time to review my manuscript. I've made some revisions based on your comments. The revised document is at the same URL.
> > It is probably > > more convenient to have a simple tool that produces sample > > notifications on command. > > I wrote just such a tool: > > https://bitbucket.org/boredzo/simplest-notifier-evar/downloads Thank you very much for this reference. It is a better tool than my AppleScript. The web document now includes a link to this application instead. > > Unfortunately, the present Growl networking implementation has one > > key user-interface limitation. It cannot differentiate between > > applications registered locally or remotely. So if you have Growl > > notifications going between two computers running the same Email > > reader or browser, you cannot use the mechanism above to turn off > > notifications from remote computers while keeping notifications from > > the same application generated locally. > > Food for thought here. Has this problem not been seen before? It certainly didn't take long for our home network to be swamped with unwanted notifications from each other's computers. > “Zombie” actually has a specific meaning that doesn't apply here. The > problem that people have been reporting is that Growl on the receiving > computer will hang; you can just say that, and it'll be correct. Well, the end-user audience was extremely unlikely to have anything but the Hollywood sense of zombie in mind. That was very much the analogy I wished to harness in order to help them understand why they might need to use Activity Monitor. Nonetheless, I have reworked the text in this section and substituted the phrase "undead." I hope that will motivate the same sort of analogy for why "force-quit" might be necessary. > > When you press the Quit Process button, you'll be given a choice of > > either having the application quit, or using the operating system > > services to force GrowlHelpApp to quit. Try simply quitting, … > > If Growl is hung, that will not work. It would need to respond to the > Quit Apple Event, and a hung process isn't responding to any Apple > Events. Yes, I understand that. However, I'm not so optimistic as to hope I've covered all the possible ways end-users break their Growl installations. I've rephrased this section to explain why quit won't work for GrowlHelperApp in a nonresponsive state. Asking end-users to try a simple quit first may be of help in diagnosing their problems. Thanks again for your feedback. Any additional comments would be greatly appreciated. Sincerely, Edouard -- 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.
