growl /

Filename Size Date modified Message
Bindings
Common
Core
Developer Tools
Docs
Extras
Framework
Growl.xcodeproj
Plugins
Release
StatusItem
Tools
Unit tests
external_dependencies
images
xcconfig
193 B
1.4 KB
525 B
593 B
25 B
1.5 KB
3.3 KB
4.1 KB
647 B
1.8 KB
37 B
WHAT IS THIS?

bitbucket.org/pmetzger/growl is an unofficial patched version of the
Growl 1.2.x sources taken from the last available public source tree.

The branch builds cleanly under XCode 4.1. As provided, it constructs
binaries that run only under Mac OS X 10.7 "Lion", though people
running Snow Leopard are probably better off using the official 1.2.x
binaries anyway.

This branch also incorporates a patch for HardwareGrowler.app, which
otherwise crashes on Lion if your WiFi adapter changes state.

None of this work is official, it is not endorsed by the growl.info
folks, it is not guaranteed to work at all.

(The tip of this tree is the "fork-1.2" branch, which was branched
from the "maintenance-1.2" branch. The "default" branch seems to be
old and unused.)

BINARIES:

Binaries, version numbered "1.2.2f" to distinguish them from 1.2.2,
are available in "Downloads" on my bitbucket.org page. They were built
using the "HOW TO BUILD" directions below. The only one of real
interest is probably the patched HardwareGrowler which doesn't crash
under Lion.

On my own machines, I am running the growl prefpane itself,
HardwareGrowler and GrowlTunes, but I wouldn't call that "extensive
testing", and I haven't properly tested the other Extras -- you have
been warned!

HOW TO BUILD:

0) You need be running Lion and have XCode 4.1 installed
1) Clone the repository.
2) Run "make" in the "Release" directory. This will build the entire
   system and generate .dmg files for the release that can be found as
   Release/build/Growl-*.dmg
   It is probably a good idea to do something like
   "make >/tmp/log 2>&1" and make sure when it is done that
   /tmp/log contains no "BUILD FAILED" lines.

BRIEF HACKING GUIDE:

0) Build output is located in "building" directories that are
   scattered in the various XCode projects in the tree. The main
   project builds the Growl prefpane and framework. "Extras" contains
   the sources and projects for the various plugins like GrowlTunes.
1) The "./build.sh" script in the top directory may be of some small
   use, if only for reading.
   After it runs, a zip file of the growl preferences will be left in
     build/Release/Growl.prefPane.zip
   To install it by hand for experiments
     a) Make sure you have no other version of growl installed or running.
     b) cd to ~/Library/PreferencePanes and unzip the thing there.
2) .app files for HardwareGrowler, GrowlTunes, etc, are in
   Extras/<extraname>/build/Release for each of the extras.

WHY DID I FORK THIS?

[UPDATE: As of Tuesday, October 11th, I have been banned by
Christopher Forsythe from the growl mailing lists, apparently for
telling people that I'd forked the code and where to find it. Sadly,
this does not seem like a promising development.]

I forked the Growl sources largely because Growl 1.3, available only
on the Mac App Store, seemed to fail very badly for most of the people
who installed it (including me), and the growl developers seemed
fairly unsympathetic to people's complaints, claiming that there was
no way they could have known of the various installer bugs it has, and
that the failure of applications using old frameworks to talk to the
new growl is the fault of the app developers. The 1.3 distribution
also lacks working versions of the various "extras" that were in the
past distributed with Growl.

I think the developers should have withdrawn 1.3 until the problems
were fixed, but they felt otherwise.

Unfortunately, the Growl 1.3 sources are not currently available to
the public, so it is not possible for me to simply fix those sources
for myself and submit patches back to the developers.

I would simply have continued using Growl 1.2.2, but the old
HardwareGrowler was failing pretty badly for me under Lion, and I both
wanted that fixed and to know that, if I needed to continue supporting
Growl just for myself, that I could.

Hopefully the Growl 1.3 branch from the official Growl maintainers
will eventually become open source again and get straightened out so
that it works for most users, but if it doesn't, a fork of the project
will be able to provide a working Growl to Mac users.
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.