With a growing number of apps on Mac OS X being delivered with Growl notifications, I find myself wishing that the default behavior of growl was not just display only, but something more actionable. That is, I want something like a configurable Growl client that could ‘subscribe’ to certain Growl notifications (Growl Actions?) and then take action based on them. This would make all of the apps that participate in the scheme much more flexible and powerful using a common mechanism (growl).
For example, if you use Twitter or Jaiku and that client could subscribe to a Growl notification that a batch update to your files in Aperture had just completed and send you a corresponding Twit. Another app might then perform some file housekeeping action based on the same notification having been sent (so one GrowlAction, multiple ‘subscribers’ take action on it. Some of this could probably be done with Applescript, but using Growl feels like a more open and extensible solution (and keeps it open to our Linux brethren). Heck, this could even lead to Growl-based mashups on your desktop (and beyond).
In conjunction with this concept of Growl Actions, I thought it would be handy to have an app/widget that I call a Growl-er (think flower). This is a circular visual widget that would compactly display received growls; hover over a ‘petal’ and it would extend out and show more detail about the growl received. When a Growler becomes too cluttered it could ‘sprout’ another circle to populate.