future development on callbacks?

[H.Mijail]

Hi there,

I have been looking for info on callbacks usage, and am a bit dismayed
to see that they seem only useable in Cocoa: no scripting support, no
growlnotify, no nothing.

Furthermore, even general behaviour of waited-for notifications
(growlnotify -w) seems buggy; I just noticed that if I have two
different notifications waiting, each having been created through
different growlnotify's, clicking on one of them dismisses both. So if
that is buggy, I'd guess that callbacks will be doubly so.

And coincidentally, I am looking for an excuse to get into Cocoa / OS
X development, and this could just be it.

So I would like to know what are the plans about callback support in
near-future versions. Are there any plans to work on them? I see focus
for 1.3 will be on GNTP, but that could imply also something about
remote callbacks, which could mean lots of changes, which could mean
it's not the best place to start...

My programming background is C / Java / Applescript / starting
python.

Regards.

[Peter Hosey]

On Nov 19, 2009, at 14:59:16, H.Mijail wrote:
> I have been looking for info on callbacks usage, and am a bit
> dismayed to see that they seem only useable in Cocoa: no scripting
> support, no growlnotify, no nothing.

One person suggested making growlnotify indicate feedback via the exit
status, which would work, but nobody's implemented that. Nobody's
implemented feedback for AppleScript scripts, either.

> Furthermore, even general behaviour of waited-for notifications
> (growlnotify -w) seems buggy; I just noticed that if I have two
> different notifications waiting, each having been created through
> different growlnotify's, clicking on one of them dismisses both.

Interesting. Filed:

http://code.google.com/p/growl/issues/detail?id=60

> So I would like to know what are the plans about callback support in
> near-future versions. Are there any plans to work on them? I see
> focus for 1.3 will be on GNTP, but that could imply also something
> about remote callbacks, which could mean lots of changes, which
> could mean it's not the best place to start...

The feedback aspect of GNTP is based on how Growl does feedback, so
nothing will change from the API standpoint (except that we'll add
notification-closed feedback at some point). It also shouldn't hold up
anybody who wants to implement feedback for AppleScript.

growlnotify just uses the Cocoa API.