On Sat, Oct 08, 2011 at 12:47:49PM -0700, Peter Hosey wrote: > On Oct 8, 2011, at 12:17:58, Richard Johnson wrote: > > 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. > > The change that broke applications that use old frameworks wasn't an API > change (which would be *in the framework*). > > The change that broke old frameworks was the move from a .prefPane to a .app.
That was part of the API, in actual practice. Your arguing differently does not change the fact that the programming interface used by many applications (the API) to find Growl and to send notifications for display by Growl was changed. Further, that deliberate and ill-thought-out, ill-planned-for change broke apps that users were relying upon. <sigh> > No APIs were removed in any hitherto released version of the framework. You broke Growl for the majority of users with your changes. This was deliberate on the part of the dev team, though perhaps without a full understanding of the consequences. You need to own that and provide clear communication about how you're fixing it. The continual insane nitpicking denial we're getting instead doesn't play well, especially when it's now a for-pay application. Am I going to have to change my advice to "Find an alternative to using Growl, as the developer community is off the rails, and Growl thus will be an utter train wreck for the foreseeable future." Best of luck! -- 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.
