On Monday, October 28, 2013 6:38:07 AM UTC-5, Philip Chee wrote: > On 28/10/2013 16:02, Florian Bender [:fbender] wrote: > > > Mac OS X Mavericks has been released with improvements to NC. Safari > > > uses NC to display Web/PushNotifications and seems to work quite > > > well. > > > > > > I'd like you to revisit the decision to drop NC in favor of XUL > > > Notifications, and have a second look at the new API and > > > > Nitpick. NC wasn't dropped. We never supported the OS X NC at all. There > > was some preliminary work but that was never checked-in to mozilla-central. > > > > > capabilities. NC support could be limited to 10.9 to reduce > > > maintenance cost (luckily, nearly everyone is eligible for the free > > > update which means that earlier versions could fade into irrelevance > > > sooner than later), and keep the XUL Notifications for 10.6-10.8 (as > > > long as these versions are supported and have a meaningful market > > > share). > > > > I believe that this is one of those "patches welcome" occasions. > >
This is what I do not understand. If the Growl framework had simply been updated instead of removed, then you would have been able to support 10.6 -> 10.9 without any more maintenance than updating the framework. There are references to why the framework was removed, but nothing specific. Now I have end users coming to us confused as to why Firefox and plugins for FF, along with Thunderbird are all not notifying through Growl. Which is really frustrating because I cannot for the life of me figure out from all of the tickets why exactly Growl support was removed. I asked on a bug but apparently that was the wrong place to ask, so I'll ask on this thread which was linked. I'll copy what i wrote over there: I would also like to find out why Growl was removed. We're getting user complaints because users don't understand why their firefox plugins are not notifying through Growl anymore. I'd like to explain it better than "because someone at Mozilla arbitrarily decided to remove it instead of talking to us about what features they needed". Which so far is exactly how it looks. I just need a simple 1-3 sentence explanation that I can send to my end users as to why a feature they depended upon is no longer present. I would also like a much more technical explanation as to why Growl support was removed because obviously we'd like to address those kinds of issues going forward. What I do not understand is that the feature for this was developed in our repository. The framework was paired down to work with the very stringent requirements that Mozilla has in order to get Growl support to work. The framework we provide now supports native notifications on 10.8 and 10.9. On 10.6 and 10.7 there are no native notifications so Growl is the only game in town, but you do not need Growl in your application, just the framework, in order to fire a notification to the end user. We could have made the adjustments to our notification framework to give not only Mozilla what they wanted, but also provide those changes to the entire mac community that uses our framework. So if someone explains exactly what the problem is, we'd be happy to look at addressing those things. Hopefully you can see why this is frustrating to me, and more importantly to our mutual end users who are the ones who are affected by this (currently) seemingly arbitrary change. Chris Forsythe Project Lead - The Growl Project ch...@growl.info > > Phil > > -- > > Philip Chee <phi...@aleytys.pc.my>, <philip.c...@gmail.com> > > http://flashblock.mozdev.org/ http://xsidebar.mozdev.org > > Guard us from the she-wolf and the wolf, and guard us from the thief, > > oh Night, and so be good for us to pass. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
