Why discourage the use of growlnotify?

[Kevin Walzer]

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

[Chris Forsythe]

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

--

You received this message because you are subscribed to the Google Groups "Growl Development" group.

To post to this group, send email to growl-de...@googlegroups.com.

To unsubscribe from this group, send email to growl-developm...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/growl-development?hl=en.