Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Jun 23, 2012
  1. Add loadedConfig() config handler

Commits on Jun 21, 2012
  1. Comment fix

  2. Add Makefile and .gitignore

  3. Update to Growl development team's recommendations.

    This will check to see if Growl is running before sending
    notifications, and it will look for Growl by bundle id instead of by
    name.  (The latter removes the problem with the different application
    name between Growl 1.2 and 1.3.)
    Thanks to Chris Forsythe (the lead developer of Growl) for the
    information.  This is based on his commit on
    7a974c2, but was edited to fit in
    with the other changes at the same time.
  4. Remove dependencies on System Events.

    This is an external application that can take several seconds to
    launch and load.  I wasn't using System Events for anything that can't
    be done with internal AppleScript commands (some of which still need
    to talk to current application, but we know that's running).
  5. Add user-configurable callbacks.

    One of these is shouldNotify, and this commit also adds ignoreBuddies
    to its capabilities.
    This requires a change to the "on growl" signature, since I want the
    user hooks to have some consistency in some of the parameter names,
    but also want the hooks to not need iChat's terms.  This means that
    the "status" parameter was changed to "showingStatus".
  6. Add a user config file.

    This is cherry-picked from a large batch of changes I made at the same
    time, so it might be broken without the next few commits.
Commits on Oct 25, 2011
  1. Merge pull request #1 from cblage/master

    Fixed notifications appearing in tabbed windows when the sender is the frontmost tab/window
Commits on Oct 24, 2011
  1. @cblage

    Not showing notifications for multi-tabbed windows when the sender is…

    cblage committed
    … on the frontmost tab/window
Commits on Oct 4, 2011
  1. Update to the Growl 1.3 API

Commits on Sep 21, 2011
  1. Make the source ASCII only.

    AppleScript uses Mac-Roman or UTF-16 (with a BOM); at least, that's
    what AppleScript Editor saves in .applescript files.  (For what it's
    worth, .scpt files have text objects in both Mac-Roman and UTF-16,
    with the Mac-Roman version using ? for unencodable characers.)  Since
    git doesn't have a mechanism to specify a file's encoding (it sees
    file contents as binary blobs, except that it'll sometimes edit the
    line endings), it needs to be saved in one of those formats if we want
    a checkout from git to work as a .applescript file.  But, github will
    display it as ISO-8859-1.  (The raw view sets the Content-Type, and
    the web view will translate it from to UTF-8 and send it to the
    browser that way.)  If a user does a copy/paste from the browser into
    AppleScript Editor (like my blog says to do), then they'll get a
    different character.  To allow either a git clone or a copy/paste from
    github to work, we have to use ASCII.
  2. Add auto-accept feature, and include status messages in notifications

    Remove history comments, since we're now moving this to Git
    (autoAccept, buddy authorization requested, received text invitation,
    received audio invitation, received video invitation, received local
    screen sharing invitation received remote screen sharing invitation
    (currently commented out), received file transfer invitation): New
    property autoAccept.  Handlers changed to add autoAccept capability.
    (growl): Added "given status" flag, which shows the buddy's status as
    the text and the message as the title (useful for when a buddy's
    status changes).  All handlers changed to specify with/without status.
    (growl): Cleanups: move some foo...end foo blocks to one-liners.  Tell
    application "iChat" as a literal app name, to help AppleScript Editor
    recognize the dictionary in use.
    (growl, buddy authorization requested): Add some missing local
    declarations, and combine a few from multi-line to one line.
Something went wrong with that request. Please try again.