I asked Ryan if we could include it, I think he said he'd rather host it himself.
I'm glad it worked out, I can't think of any reason it would not continue working with 1.3. I don't expect any feature around this being implemented in Growl itself in the near term, so I think this is your solution for now. Chris On Aug 23, 2011, at 2:38 PM, david koff wrote: > dear english breakfast, > > so far, so good. initial testing of changing the permissions on the ~/ > Library/Application Support/Growl/Tickets directory seems to be > working out quite nicely. it's a temp solution of course until 1.3.3 > comes out but it gets us what we need, thank you. and ryan collins > plug in is sweet. something to consider bundling with 1.3.3 once you > release it to the masses and i get me some time to learn more about > CSS and RGBa calls. > > cheers, > chamomille/rooibos > > > > On Aug 17, 12:18 pm, Chris Forsythe <[email protected]> wrote: >> On Aug 17, 2011, at 12:28 PM, davidkoffwrote: >> >>> chris, josh: >> >>> a fine idea: i'll start over, apologize for my misunderstandings and >>> just say, we love growl enough that us sysadmins here want to use it >>> for one specific task: as a unique and customizable way to message the >>> desktops of our users. that's it. compared to other messaging options, >>> you should know: growlnotify is a WINNER of a solution. probably the >>> best i've seen yet. and i've been a mac sysadmin for 15 years. it's >>> customizable in so many ways as to make the other options >>> (applescript, bash, HUD) look like yesterday's solution. seriously. >>> from the sysadmin perspective, just that one portion of your software >>> is a gold mine. >> >> Glad to hear it, and no worries. It's easy to misconstrue something on a >> medium which is very one noted. >> >> I do think you guys are going to miss out on some cool stuff, but at the >> same time it's not what you need. >> >> >> >>> the problem is that - after reading the thread that josh suggested and >>> the tech notes on the growl framework - it's clear that other apps >>> with the growl framework auto-register with growl and just begin to >>> pop-up their own messages. and there doesn't appear to be a way to >>> prevent that... or is there? why would we want that? the answer to >>> your question is that, when beta-testing our growl deployment, the one >>> critique we repeatedly got from our colleagues was: although we love >>> the look/functionality of new alert messages you're sending us, why >>> are all of these OTHER messages from other applications suddenly >>> showing up? we don't want those! >> >> Alright, if they can tell you why then I'd like to know why. Information >> like this is crucial to our improvement of Growl going forward, so if you >> have anything specific feel free to send it to the list, or to me directly. >> >> That said, I think I came up with a real solution for this about 3 or 4 >> months ago (not tested, just thought it up) that I'll detail below. >> >>> so, a few suggestions/questions: >> >>> 1) is it possible to separate growlnotify from the rest of the pack >>> since it would seem (after reading the threads) that a lot of folks on >>> enterprise want to use JUST that for messaging to desktop without the >>> other clutter? >> >> Ya, actually we're looking to do something like this in 1.3. Essentially the >> framework which is included in 1.3 will have a mini notification in it. It >> will not be configurable other to enable/disable it for the end user. >> Theoretically you could just modify it to look how you want and there you >> go. Or suggest improvements. This is more of a long term solution. On to the >> short term solution. >> >> Growl requires that an application have a ticket in order to display a >> notification. Applications must register with Growl, and Growl generates the >> ticket file based on their registration requirements. If Growl cannot write >> the ticket to its tickets directory, then it cannot do anything about it. I >> have not tested this, but this is the basis for the solution, which is why I >> needed to know what you were looking to solve. >> >> Look at a base Growl installation in your test environment that has more >> than 1 ticket, or even 1 is enough. Then look in ~/Library/Application >> Support/Growl/Tickets. Set the directory and the ticket to readonly instead >> of read/write. That should in theory address the main issue you are having. >> >> Now, if any of your users notice that Growl is installed and expect that >> Growl should work how it normally works, then you'll need to have a response >> for that. Also, keep in mind that the 1.3 version of Growl will be 10.7+, >> but will also have added functionality of the rollup window and things like >> that. However, I think this sort of explains what I was thinking might solve >> the problem. >> >> Now, as to displays, I think you should look at one we do not ship if you >> have your end users on safari 5 and/or >> lion.http://www.ryancollins.me/?p=92I've tried out just last night and it's >> pretty awesome. Plus if you're any good at css/xhtml you can use it as an >> example of how to make a custom one that has your company logo in it, or >> something along those lines (this one might be extreme, it has no images for >> instance). >> >>> 2) is it possible to deploy growl across our network with those "auto- >>> activate" features turned off, at least initially, if possible. this >>> way, the power is still in the hands of the user, and we're just >>> setting an "initial deployment" state. >> >> You can repackage the prefpane and handle it like that perhaps. If you know >> package maker our source is open so you could kind of see what we did and >> minimize the work. Look in the Release directory for our build system in >> 1.2.2. >> >> >> >>> as for black tea: are you a darjeeling or a Lapsang soughing kinda >>> guy? seriously: i do like chamomile. and rooibos since we're sharing. >> >> More of an english breakfast kind of guy myself. I don't find darjeeling to >> be that favorable, but I've never heard of lapsang. Then again once you make >> it weak tea with honey and milk, I don't know that it matters that much. >> Since we're sharing :P >> >> Chris >> >> >> >> >> >> >> >>> david >> >>> On Aug 16, 2:28 pm, Chris Forsythe <[email protected]> wrote: >>>> On Aug 16, 2011, at 3:41 PM, davidkoffwrote: >> >>>>> chris: >> >>>>> i posted a polite and descriptive question to the forum. >> >>>> My question was polite. Rather than just assume as to why you were asking >>>> what you were asking, I wanted more information first before knee jerking >>>> a response of "oh go do this". I figured you would like an answer that >>>> actually solves the problem rather than just a guess as to what the >>>> problem is. As a sysadmin myself I tend to prefer to know the root cause >>>> of the problem before trying to address it, rather than applying a bandaid >>>> solution. I'm sure you can understand that since you are a sysadmin >>>> yourself. >> >>>>> rather than >>>>> answering my question, you instead challenged why i asked it. it >>>>> doesn't MATTER why i asked the question, brother: as a sysadmin, i >>>>> have a task i need to accomplish. so i politely responded for what i >>>>> wanted a second time. you countered with a really mean and heartless >>>>> reply. >> >>>> It wasn't mean at all, I was simply explaining why I wanted you to simply >>>> explain what's going on before I answer. I'm sorry you took it as mean, >>>> but it wasn't meant that way. Email is not a face to face conversation, >>>> reading into things is really a poor idea in my experience. No disrespect >>>> meant, I seriously wanted to know what I asked for, and that's it. >> >>>>> and you did it on a public board for everyone to see. i thought >>>>> this was a discussion forum for growl, >> >>>> It is a discussion venue that you can use via the web or via email. As >>>> such, I wanted to discuss it before going "oh here, do this". As it is the >>>> solution I was thinking of likely will not work depending on your >>>> scenario, so I really, really do need to know why you are doing what you >>>> are doing. >> >>>>> not a vehicle for you to flame >>>>> folks who like the software and have invested time in trying to work >>>>> with it. >> >>>> And it's not a vehicle for you to flame the people who want to help you. >>>> So far you have yet to actually explain the reasoning behind what you are >>>> doing. >> >>>>> I guess i was wrong. >> >>>> No, you're right. Except you're wrong that you read into what I sent more >>>> than was actually there. >> >>>>> you take care. and maybe get a cup of chamomile tea... >> >>>> I actually prefer black with a spot of honey and milk. That doesn't help >>>> you though. I would suggest you drink that tea you're offering me, think >>>> about what I asked, and then answer my question. Simply put I want to know >>>> why you are doing what you are doing so that I can answer the questions >>>> correctly, that's it. >> >>>> We've been working on Growl for a very long time, and as you can see it's >>>> only recently that administrators are asking us questions about how to fit >>>> Growl into their environment. I'm not going to assume that every >>>> administrator has the same reasoning behind what they are doing, so I >>>> really do need to know why you are doing what you are doing. If you do not >>>> want an answer, then you've really just wasted our time simply because you >>>> didn't want to type out why. That seems silly, you have the people who >>>> work on the product you want to deploy answering you directly and you want >>>> to have a fight about how one question was phrased that you don't want to >>>> answer but that would help us immensely in solving the problem you are >>>> having. >> >>>> Help us help you. Bottom line, answer my question and we can move on. If >>>> you instead want to talk about the limitations of a class 5 language like >>>> the English language, then feel free to do that but I probably will not >>>> continue responding. I do not feel my question had any vitriol in the >>>> slightest, and would have been easy to answer and gotten you a faster >>>> answer if you had not read it that way either. >> >>>> Let's start over. Please tell us why you want to do what you are wanting >>>> to do so that we can better answer the original question. >> >>>> Chris >> >>>>> On Aug 16, 12:23 pm, Chris Forsythe <[email protected]> wrote: >>>>>> That's not what I asked, I need to know why so that I know how to answer >>>>>> your question. So please answer what was asked. >> >>>>>> Chris >> >>>>>> On Aug 16, 2011, at 2:19 PM, davidkoffwrote: >> >>>>>>> is it possible, please? >> >>>>>>> On Aug 16, 11:45 am, Chris Forsythe <[email protected]> wrote: >>>>>>>> Why would you want this? >> >>>>>>>> Chris >> >>>>>>>> On Aug 16, 2011, at 1:42 PM, davidkoffwrote: >> >>>>>>>>> my situation is this: >> >>>>>>>>> i manage a network of several hundred macs. i've used JAMF's composer >>>>>>>>> tool to successfully snapshot the growl installation. in my snapshot, >>>>>>>>> i'm only activating growl notify and have set up that application with >>>>>>>>> a particular set of window colors and so forth. however, once >>>>>>>>> deployed, although the deployment works like a charm, ANY OTHER >>>>>>>>> application with the growl framework auto-detects the >> >> ... >> >> read more ยป > > -- > 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.
