On Sun, Aug 10, 2008 at 3:36 PM, Alex Boisvert <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 24, 2008 at 5:02 PM, Assaf Arkin <[EMAIL PROTECTED]> wrote:
>
>> == Growl
>>
>> For those of you running on OS X and have Growl installed (which I'm
>> told is practically everyone running on OS X), I added Growl
>> notifications for completed and failed builds. You can turn them
>> on/off from the Growl notification pane. I heard that Growl is coming
>> to Windows and there's an alpha out.
>
>
> As a general mechanism, I'd like to suggest that Buildr could use the
> BUILDR_NOTIFY environment variable to check if notifications should be sent
> and use its value as a system command, substituting the literals {type},
> {title} and {message} for their corresponding values.
>
> For example, on my system I would define:
>
> export BUILDR_NOTIFY="qube -i \"{title}\" \"{message}\""
>
> to use Qube <https://launchpad.net/qube>, a libnotify client on Ubuntu
> Linux.
>
I've actually changed my mind on this and decided to remove it. Instead of
pushing the integration at the OS/shell level, and fiddling with environment
variables and shell scripts, I think it's better to have people hook
directly into the completion callbacks by writing Ruby code (e.g. in the
buildr.rb user settings file). I'll document the approach in "Other
Stuff" with an example.
When Growl-like notifications become more standard across Linux distros,
I'll be happy to bake tighter integration into Buildr.
alex
