A massive +1 to that - I've also told our team exactly the same. On 8 Oct 2011, at 20:17, Richard Johnson <[email protected]> wrote:
> On Sat, Oct 08, 2011 at 12:18:23AM -0500, Christopher Forsythe wrote: >> On Fri, Oct 7, 2011 at 9:39 AM, Perry E. Metzger <[email protected]> wrote: >> >>> On Fri, 7 Oct 2011 07:16:33 -0700 (PDT) K <[email protected]> >>> wrote: >>>> I uninstalled via appcleaner the latest growl.. i reinstalled it.. >>>> now there are no applications listed and no way to add >>>> applications. i've done this twice now. any ideas? >>> >>> Yes. Back out your upgrade to 1.3, which is pretty much >>> non-functional for most people. Then request a refund from apple. The >>> developers should pull 1.3 until things work correctly but they seem >>> to be unable to admit in public that they made a tremendous mistake. >>> >> This is not the answer to his question, you will be removed from the list if >> you do this again. > > Hmm, I thought Perry's response was in fact in direct answer to the > question about how to fix the problem of desired notifications that used to > work no longer showing up in Growl 1.3. > > It is in fact identical to the advice I'm going to be giving to our Growl > users. That is: "Do not install Growl 1.3. 1.3 was prematurely released, > with major changes that almost certainly break the notifications you may > rely upon. Use Growl 1.2.2 or earlier until fixes are in for the problems > with the Growl 1.3 API changes." > > If this advice is unpalatable to you, I am sorry for any angst I'm causing > by giving it. However, users won't see the work you're doing to bring > Growl client framework use up to your modern changed version, nor will they > even know that work probably should have been done before the 1.3 release. > They'll just find the notifications they used to get no longer working. > That latter failure of functionality is what matters to users. > > Then when you add the new commercial model, and paying for something broken > into the mix, you're generating a lot of instant bad PR. Perry is not at > fault for that, nor for being perturbed (as I am) at the attitude you're > giving in regard to it. He and others, including me, are just pointing out > that the new commercial Growl 1.3 is, in practice if not your intent, > broken for for perhaps the majority who use Growl to display notifications > from the applications they use. > > If pointing that out gets folks removed from your list, well, you're > certainly welcome to your private list. It'll then be easier to develop > Grow for your own private use cases, and leave out those pesky outside > users who don't do things your way. > > As an alternative, you could acknowledge and explicitly own the breakage > your 1.3 changes have caused for the end users. Don't blame the apps > using your old APIs (and don't redefine the API to exclude common, > widespread uses, as you've tried in the past). Own for yourself that > deprecating the APIs before client apps were updated was your explicit > decision. > > From there, you could succinctly and frequently communicate progress > towards returning Growl notice functionality. You might provide a weekly > "Growl Developers Report" on known problems (with apps using old > frameworks, with crasher bugs, with other issues) and the progress being > made on remedying them [1]. > > Best of luck! > > ------- > [1] Perhaps the progress could include restoration of old APIs and a > published schedule for their retirement? I've a couple old APIs in use for > systems I maintain that we're trying to get rid of, but we're having to > wait for hardware retirement in practice. ;) Growl can probably move > faster. > > -- > 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.
