Sometimes you can't help but break compatibility, otherwise you'd never progress. The majority of the framework has been backwards compatible, that's part of the problem in a way, because developers haven't updated their copy.
Technical explanation is usually avoided at first, because for the non-technical it tends to only help confuse things, and the technical are usually more than capable of searching for the answer. I am not a dev, but from what I understand, it is one of two things: First, in older versions of Growl.framework (before 1.2.1), it assumed that Growl was a preference pane, thus now that it isn't those won't work. Now, this shouldn't have been a major issue: as far as my emails tell me, version 1.2.1 was released at least by the end of January 2010. But application developers haven't upgraded. (Through the course of the last few days, I even found a Growl.framework version 0.7.something! That's from before I even owned a mac) I suppose in retrospect*, maybe that should have been anticipated/talked about more than it was (developers were warned a while ago, maybe not enough). Second, one of the functions (namely, isGrowlInstalled), even in the latest 1.2.x frameworks returns false for Growl 1.3 (again because it's looking in the wrong place). This wasn't expected to be a major problem afaik because the official guidelines are for the app to send notification requests to the framework without bothering to check, because the framework can deal with the possibility of Growl not being installed/running anyway. Some apps check this value, which is why they don't work even after dropping the new framework in. So there you have it. Yes, I agree, there may have been at least some clearer explanation. But this is what's happened, and we're all learning from it, none more than the dev team I'd guess. Also be mindful that this was only released into the wild two days ago. As I've said before, I doubt as few apps weren't Lion-compatible within two days of that being released either. Give it a month or two and I expect newcomers will look back and wonder what all the fuss was about… Josh * I mean, it's not like vast amounts of people still run 10-year-old operating systems like Windows XP, right? ;) On 5 Oct 2011, at 11:52, cstamas wrote: > I always thought it's other way around, non-intrusive _libraries_ like > Growl should be backward compatible (at least with the clients in > growlized apps), instead of nagging all the growl supporting apps to > do a release and having all the growl users waiting for that to happen > (and explaining they cannot interfere with how the apps are built and > released). > > What would be fair if Growl page in AppStore would state: > > "Please realize, that Growl 1.3 does not support currently any > application as of today, until all of those (Dropbox, Skype, etc) do a > release where they update Growl support". That as the 1st line. > > Ah yes, also "Since AppStore policies does not allow pref panes, we > made this an app, and as many apps in the wild, our paw icon is not > removable either". But at least _explain_ this about prefs pane, I got > knowledge about it by googling. > > Naturally, we made you pay for all this above :D > > C'mon, this is a joke, right? Or you wanted Growl 2.0 (that would > "kinda" justify the backward compat problem?) but it looked better as > 1.3? > > Could somebody technical at least explain _what_ is the problem > instead responding with "X app needs a release, there is a beta build > of it already".... I don't want to use Betas because I upgraded > Growl.... > > Thanks, > ~t~ > > On Oct 5, 12:39 pm, Josh <[email protected]> wrote: >> i believe that dropbox needs an update. >> there is a forum build on the dropbox forums that apparently works already. >> >> On 5 Oct 2011, at 11:09, molier wrote: >> >> >> >> >> >> >> >>> See that notifications are indeed working. Only not for Dropbox. Is >>> this a familiar issue? I deleted the entries for the growlhelperapp in >>> login items and all seems to be fine now except for the Dropbox >>> notifications. >> >>> On 5 okt, 11:19, molier <[email protected]> wrote: >>>> I had an older version running which I did not uninstall. After >>>> upgrading to 1.3 from App store I saw two versions were running. I >>>> downloaded the uninstaller to unintsall older versions which also >>>> uninstalled the 1.3 version. After that I re-installed 1.3 from the >>>> app store. >> >>>> After that I have no notifications at all. I see the growlhelperapp >>>> twice in my loginitems in my mac's system preferences. I can also see >>>> growlhelperapp is not running. Can anyone help me with this? >> >>> -- >>> 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 >>> athttp://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. > -- 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.
