On Jul 7, 12:55 am, Christopher Forsythe <[email protected]> wrote: > On Thu, Jul 7, 2011 at 2:16 AM, Dylan Ryan <[email protected]> wrote: > > Just my 2 cents. I also more or less only use growl because of growl-mail. > > Sure it's nice to get other notifications, but without growl-mail, I'd > > rather not have one more app running even if it is a very minor resource > > user. i.e. Growl Mail is the only thing that KEEPS me using Growl. Other > > things are nice but I can live without. > > GrowlMail source is freely available, you may maintain it on your own. > > > > > > > > > What kind of work goes into maintaining growl-mail? I'd be willing to > > donate my time to keeping it up to date, but I am not the greatest coder in > > the world (though I learn quickly). Every time a new OS update comes out, I > > install it day 1, and I've always just manually added the new bundle-id to > > the old version of GrowlMail's .plist and it has always worked for me on > > both 32 and 64-bit intel machines, so (at least so far) no major changes > > have been *necessary* that I've seen. If it's just adding the new IDs and > > (possibly many) minor internal changes (and rebuilds), I can do that no > > problem (I have access to a 64-bit intel MBP that I always keep up-to-date, > > a 32-bit intel MBP that I can either keep up-to-date or lag a version if > > needed, and PPC machines on Tiger as well, so I can test on a fairly wide > > spectrum of hardware and software). > > > Can you give us more info on what the changes it typically requires are? > > Check the release notes and tickets, those are the best things to look at. > > > If I think I can handle it, I'll take full responsibility for getting > > things done promptly and keeping it alive for as long as I can. (In all > > likelihood, I'll just be building my own versions from source if it dies > > anyway, so I may as well help the project out instead of being selfish about > > it). > > The problem is that then GrowlMail becomes the only thing we ship that is > still a distraction. In four months say you don't want to do this anymore, > then we have to kill it yet again. > > > I am less interested in handling Growl-Safari, as I personally do not use > > it much and given what you just said, it sounds beyond my ability. Though as > > long as it *isn't* a major headache, I can handle minor changes to it > > (that is, I am willing to keep it alive for as long as my skill allows me > > to, if people are interested). > > I'd say take on what you like. > > We haven't sent the official email about the details of GrowlMail being > retired yet, please wait for that first. > > Chris > > > > > Dylan > > > On Jul 7, 2011, at 12:03 AM, Peter Hosey wrote: > > > On Jul 7, 2011, at 00:00:09, ravedog wrote: > > > What is the logic behind killing GrowlMail and Growl Safari other than they > > are plugins for Apple apps. DO you have to kill them to gain entrance into > > the store? > > > Growl could get into the store regardless of whether we kill GrowlMail and > > GrowlSafari. > > > GrowlMail has been a terrible support burden, as much work to maintain as > > all of our other products combined. GrowlSafari is fragile internally, so > > while it hasn't caused us many headaches *yet*, it's only a matter of time. > > > So, we're killing both of them. This will free up the time we'll need to > > make all the necessary changes to Growl and leave us plenty of time in the > > future to maintain all of our surviving products.
makes sense. just sad. I can wrote Applescripts to do it I guess. > > > Also, will it still be fully AppleScriptable and have the same dictionary? > > > That's the plan. > Awesome on the AppleScript (thats how I use growl)... I forgot to ask... will Prowl work? -- 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.
