No worries, glad to have clarified it. Obviously we didn't relay this as well as we could have, so I need to figure out how to do that. We had been looking into setting up a blog, but I don't know if that's the best route or something else.
http://growl.info/documentation/developer/implementing-growl.php#mist documents the fire and forget display, called Mist. It may be of some further interest to you. Let me know if any of that needs to be expanded on. :) -- Chris Forsythe On Friday, November 4, 2011 at 9:59 PM, Emery wrote: > Oh, well I sincerely apologize. If Growl still offers basic > notification functionality for free and the app just enhances control, > that completely debases my complaint and is entirely reasonable. I > didn't research before complaining. I totally support the decision now > and think you did the right thing. Keep up the good work! > > On Nov 4, 6:56 pm, Chris Forsythe <[email protected] (http://growl.info)> > wrote: > > I think you are only seeing part of the picture and making assumptions > > based on that. We accounted for Developers not wanting to tell their users > > "hey go spend 2 dollars to get notifications!". The 1.3 SDK includes the > > 1.3 framework, which provides a notification built-in. If a user wants to > > configure those outside of what the Developer provides, then they would > > need Growl. > > > > On another note, to be quite honest I was about a month away from killing > > The Growl Project overall until the start of what we have now was put into > > the motions. We chose this option instead, and overall it is a pretty good > > move for us. You'll have your opinions that you've stated here, and I doubt > > I'll change those with what I've typed. So we'll just have to see. I will > > say that we talked to a lot of Developers of applications that work with > > Growl prior to making this choice, and they all were pretty positive about > > the change. > > > > -- > > Chris Forsythe > > > > > > > > > > > > > > > > On Friday, November 4, 2011 at 5:23 PM, Emery wrote: > > > Of course paying $2 for a good piece of software is not a big deal, > > > and I am not a FLOSS nut. But I think this move is uniquely unethical. > > > People used Growl as a simply, de-facto standard extension to the OS, > > > a simple notification service. Developers use it for its ubiquity, and > > > its ubiquity came from developers using it. To suddenly begin charging > > > seems dishonest. The move will also will ultimately degrade its > > > ubiquity, and lose its value. As a developer, I obviously will not be > > > supporting Growl notifications anymore, and look forward to the FLOSS > > > alternative that inevitably supersedes it. > > > > > > > > > > -- > > > 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] > > > (mailto:[email protected]). > > > To unsubscribe from this group, send email to > > > [email protected] > > > (mailto:[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] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[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.
