(I am not, nor have I ever been, an Applescripter. It hasn't changed much, but if we change it the API is for scripters, who by all rights should be able to change their scripts with minimal effort.Ģ) You can crash GrowlHelperApp via Applescript, or your own application, if you don't do it right. Some application developers are hesitant to include amework in their application, that's fine, so they send notifications via Applescript.ġ) The Applescript API is not guaranteed between releases. You folks do have another option, but it isn't guaranteed. The framework can work with Carbon or Cocoa. amework gives you what you need to send notifications, along with, as the name says, an installer to install Growl. amework gives you what you need to send notifications. The download itself includes 2 frameworks, amework and Growl.Framework. This includes a bunch of images, and all the Extras code, and all the Growl code, and all the Framework code, and the Release directory, and so forth. > guessing applications don't really distribute themselves with the full package?
> 2) How large is the framework? The download was 7 megs I believe, but I'm Ripping code out of the framework and putting it into (I hope I'm reading bugzilla right) Thunderbird would amount to very small space savings. > 1) How much of the growl framework do we need to include in our builds?Īll of it? The framework is designed so that it gives you backwards compatibility should we upgrade to a new system in 1.1, or something like that. You've got a few options actually, I'll explain below.
> We just need to hook up the code to turn that into a growl notification. > already got a C++ object that's mac OS X specific and knows all the details > started browsing over the growl documentation, but am not a Mac expert. > Chris, I'm interested in kick starting this project for Thunderbird. cc'ing Chris over at the growl project who has commented on the Firefox bug for
0 kommentar(er)
