Grab the 0.7.6 disk image and see if the scripts there will help you out on this script.
Chris On Tue, Nov 30, 2010 at 8:39 PM, jonhollander <[email protected]> wrote: > I wrote a crude Applescript to mimic the functions of GrowlMail until > it gets updated to work with 10.6.5. > > To use it, save the script below to your "Mail Scripts" folder. Then, > create a rule in Mail that is executed on every message (or any other > criteria you like) and calls the script. > > I'm not sure what problems arise from using this script instead of > GrowlMail (as alluded to above); the script seems to work fine for > me. > > Feel free to use/modify/abuse this script anyway you like. I love > growl and saw a chance to give a little something back to the > community. > > Jon > ------------------------------------------------------------------------------------ > --Growl New Mail Notification Applescript > --Written by Jon Hollander 11/30/10 > > --For testing, comment out the next two lines > using terms from application "Mail" > on perform mail action with messages theMessages for rule theRule > tell application "GrowlHelperApp" > set the allNotificationsList to {"Mail Received"} > set the enabledNotificationsList to {"Mail Received"} > register as application "Growl Mail Applescript" all > notifications > allNotificationsList default notifications enabledNotificationsList > icon of application "Mail.app" > end tell > > tell application "Mail" > > --For testing, uncomment the next line, select one or > more messages > in Mail, and run this script from script editor. > --set theMessages to the selection > > repeat with thisMessage in theMessages > set thisSubject to subject of thisMessage > set thisContent to content of thisMessage > > --Limit description to a reasonable length - > text parsing could be > improved to strip leading/excess spaces and carriage returns > set thisLength to length of thisContent > > if thisLength < 200 then > set descriptionLength to thisLength > else > set descriptionLength to 200 > end if > set thisNoticeText to text 1 through > descriptionLength of > thisContent > > > tell application "GrowlHelperApp" > notify with name "Mail Received" title > thisSubject description > thisNoticeText application name "Growl Mail Applescript" > end tell > > end repeat > end tell > --For testing, comment out the next two lines > end perform mail action with messages > end using terms from > > > On Nov 21, 2:23 pm, Christopher Forsythe <[email protected]> wrote: >> We don't put out updates to pre-release versions of OS X. We wait >> until it's generally available to the public. Since Growl and thus >> GrowlMail is open source, committing the changed UUID's could legally >> be interpreted as a violation of the NDA that every developer agrees >> to when they get access to the prerelease versions of Apple software. >> >> Apple put out 10.6.5 10 days ago. 10 days is not adequate time to test >> for things like email getting deleted due to how GrowlMail interacts >> with Mail. Apple does not provide a public API, i.e. they don't >> document anything to allow for plugins. So every time they put out a >> release of Mail through OS X updates, they make every single plugin or >> mailbundle invalid through a method of requiring new UUID's. >> >> If Apple were to actually have an official plugin api for Mail, then >> we wouldn't have to update GrowlMail every single time they put out an >> OS X update. As it is I've almost thought of us changing GrowlMail to >> a script that gets added to a generic rule, thus sidestepping this >> whole cluster of not goodness. However, there are problems with that >> as well. >> >> In all likelyhood it's probably alright to just change the UUID >> strings and call it good and not test things. However, the first time >> someone lost mail we'd feel bad about it. >> >> These other developers put out an update to their product that allows >> it to work with 10.6.5 3 months ago, but did they really even test it? >> What if 10.6.5 final had different UUID's? It makes you wonder. :) >> >> Regardless, we only have 2 people who work on GrowlMail, and those two >> people have other responsibilities. Besides that, nobody on the >> project even gets paid to work on this, and we have our own lives to >> tend to first. If you want a faster GrowlMail release cycle, please >> step up or have someone else step up to take care of that. Otherwise >> it's going to release whenever we get time to release it. GrowlMail is >> not the main component of Growl. >> >> Chris >> >> On Sun, Nov 21, 2010 at 2:10 PM, ReKa <[email protected]> wrote: >> > The Signature Profiler mail plugin updated to work with 10.6.5 three >> > month ago. >> > So whats the problem with providing a working update? >> >> > On 21 Nov., 04:34, Peter Hosey <[email protected]> wrote: >> >> On Nov 20, 2010, at 14:29:38, ds1955 wrote: >> >> >> > As you know, growl mail doesn't work on 10.6.5. Somewhere I saw that >> >> > there's a beta for a version that does work. >> >> >> No, not yet. >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Growl Discuss" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group >> > athttp://groups.google.com/group/growldiscuss?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
