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.
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
> I'm not quite clear on why you are discouraging the use of growlntotify
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.