Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Growl Development
+ new post
About this group
Join this group
Message from discussion Why discourage the use of growlnotify?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Chris Forsythe  
View profile  
 More options Feb 14 2012, 8:00 pm
From: Chris Forsythe <ch...@growl.info>
Date: Tue, 14 Feb 2012 19:00:21 -0600
Local: Tues, Feb 14 2012 8:00 pm
Subject: Re: [growl-development] Why discourage the use of growlnotify?
Print | View thread | Show original | Report this message | Find messages by this author

To be frank, we provide a framework which is well tested and provides more/better features. The developers we're aiming that description to are putting it into *cocoa* applications. There is usually an exception to most rules, and this may be one.

However, AeroFS, a java application, went about this in a different way: https://github.com/aerofs/growljavabindings The reasoning they have there is pretty sound for this direction. Keep in mind that the 1.3 GrowlNotify does not talk to 1.2.2, and the 1.2.2 GrowlNotify doesn't talk to 1.3.  

--
Chris Forsythe

On Tuesday, February 14, 2012 at 10:02 AM, Kevin Walzer wrote:
> I'm working on updating my apps to be compatible with the newest Growl.
> Previously my apps had made use of the Tcl bindings for Growl support
> (my apps use Tk for their UI) or the AppleScript bindings. However, the
> Tcl bindings are now broken and the AppleScript bindings likely are not
> a long-term solution for App Store compatibility. As a result, some sort
> of update is required.

> I was looking at implementing a Tcl wrapper for the GNTP protocol (not
> fun) when I suddenly remembered the growlnotify CLI tool. Although I
> noted the docs that said "developers should not use growlntotify in
> their apps," I downloaded it, built it, and tested it with my apps, and
> to my delight it works well--better than AppleScript, which is somewhat
> brittle in the absence of a Growl installation.

> I'm not quite clear on why you are discouraging the use of growlntotify
> and advocating its use only with shell scripts. It is clean,
> straightforward, well-tested and stable because it comes from the Growl
> team itself, and is dead-simple to implement with Tcl, whose roots are
> in shell-scripting. Contrast that with implementing a new API on my own,
> with all the attendant complexity and potential for bugs, this is a
> no-brainer.

> Thanks,
> Kevin

> --
> Kevin Walzer
> Code by Kevin
> http://www.codebykevin.com

> --
> You received this message because you are subscribed to the Google Groups "Growl Development" group.
> To post to this group, send email to growl-development@googlegroups.com (mailto:growl-development@googlegroups.com).
> To unsubscribe from this group, send email to growl-development+unsubscribe@googlegroups.com (mailto:growl-development+unsubscribe@googlegroups.com).
> For more options, visit this group at http://groups.google.com/group/growl-development?hl=en.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google