Posted 16 February 2009 - 12:52 PM
Someone in the Linux/*BSD world is looking at doing something similar and people are asking "why?" but for those who use a GUI constantly, the question should be "why not sooner?"
Posted 16 February 2009 - 01:27 PM
First off, “Growl-supported apps” is a misnomer: Growl supports any application that will talk to it. It's the applications that need to support Growl. (We wrote a plug-in for Mail, an input manager for Safari, and an adapter app for iTunes, because everybody has those apps and most people use them. We didn't write an adapter for iChat ourselves because… well, we're all Adium users. ☺)
Following from that is that Growl does not watch applications. When something happens, the application tells Growl, and then Growl tells you (unless you told it not to).
Regarding the problem with pop-up menus: We know about it and will fix it in 1.1.5.
Regarding our slow pace of development: Unfortunately, there's nothing we can do about it, as we're all volunteers. The best way to speed up our development is to pitch in, if you can. This also goes for documentation.
Regarding the user interface: Yeah, it's not exactly the best. We have some ideas; we just need somebody to implement them.
Regarding the reliability problems you experienced with forwarding: Please send us specific information about the problems you experienced. If it's a bug in Growl, we'd like to fix it.
bousozoku: There's actually already a Growl-like program called Mumbles, although I do know what you're talking about (Canonical's thing, right?). There's also Guifications 3 under development?that split off from the Pidgin project, IIRC.
Thanks for the review!
Posted 16 February 2009 - 01:41 PM
Posted 16 February 2009 - 02:23 PM
Otherwise, it's so essential that I don't even notice it anymore.
Posted 16 February 2009 - 06:33 PM
Personally, my favorite thing about it is the fact that it does allow for so much user control. For instance, I have it rigged to notify me when I receive Mail. Now, that may not sound special, but because of the fine grain of control it gives the user, I've configured it so that if I'm away from the computer for awhile, it'll keep the notification on the screen for when I get back, which is great for those moments where I step away for a second and don't hear the chime of a new mail arriving in the background. On the other hand, if I'm at my computer typing away, it'll just pop up the message unobtrusively in the corner, and then will fade it out on its own after I have a handful of seconds to glance at it and see if it needs my attention.
Growl is great since it just does its job and gets out of your way. Absolutely wonderful.
Posted 16 February 2009 - 07:57 PM
bousozoku: There's actually already a Growl-like program called Mumbles, although I do know what you're talking about (Canonical's thing, right?). There's also Guifications 3 under development—that split off from the Pidgin project, IIRC.
Thanks for the review!
Yes, I believe it was Canonical, as it seemed to be an outgrowth of the Ubuntu phone interface development.
Right now, notifications (among other things) are rather haphazard on GNOME, so anything similar to Growl would be a step forward. Then again, Windows could use something also. I'm tired of Comodo Firewall Pro overlapping their dialog boxes with notifications. I mostly use my Mac but using Linux or Windows gets to be more of a pain, thanks to the work you've all done on Growl.
Posted 16 February 2009 - 07:59 PM
Posted 17 February 2009 - 03:03 AM
There is a Windows version of Growl (separate code not by us, but using our name with our permission), plus Snarl. And, as I said, there's Mumbles for Ubuntu.
Posted 17 February 2009 - 08:45 AM
Sorry for any confusion, but that's what I meant to convey -- it's the app developers that need to support Growl.
"Regarding the problem with pop-up menus: We know about it and will fix it in 1.1.5."
That's good to know!
"Regarding our slow pace of development: Unfortunately, there's nothing we can do about it, as we're all volunteers. The best way to speed up our development is to pitch in, if you can. This also goes for documentation."
I fully understand that, but for a general user (the target of this piece) it's something to be aware of -- not that it's necessarily a bad thing, unless they happen to experience a bug that needs to be resolved.
"Regarding the reliability problems you experienced with forwarding: Please send us specific information about the problems you experienced. If it's a bug in Growl, we'd like to fix it."
Basically, I'm experiencing variations on the glitch discussed in this forum thread. All of my machines use a static IP, and both are running Growl 1.1.4. If I'm on the MBP and I go to the Network section of Growl, I can see my Mac Pro in the list of available machines. On my Mac Pro, however, the MBP doesn't show in the list -- and all settings in the two machines are identical.
I should say this happens sometimes -- occasionally, the MBP shows up. But I can't figure out how/when. I'd be glad to work with you offline on this if you wish; just drop me an e-mail by clicking my name in the story header area.
Despite these minor stumbles, Growl is an indispensable application on all of my Macs -- great work!