Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Growl vs. CFUserNotification

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Growl vs. CFUserNotification

Subject: Growl vs. CFUserNotification
From: Jerry Krinock <email@hidden>
Date: Tue, 17 Mar 2009 21:45:09 -0700

On 2009 Mar 15, at 09:03, Jean-Daniel Dupas wrote (in thread "GUI Calls in Tool Executable..."):

Just to complete the answer, the correct way to display alert from a background process is to use the CFUserNotification API.

Thanks, I wasn't even aware of that. I was thinking of using Growl if my agent ever needed to speak with the user. After a few minutes of reading, it appears that ...

Advantages of Growl:
   Probably looks nicer
   Configurable by user
   Objective-C -- API looks easier to use

Advantages of CFUserNotification
   No extra framework to package
   Not configurable by user (Good if you don't want this)
   No AppKit -- safe for use in daemons

Any other Growl vs. CFUserNotification considerations that one should be aware of?

Jerry Krinock


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


Follow-Ups:

Re: Growl vs. CFUserNotification
From: Jean-Daniel Dupas <email@hidden>


Prev by Date:
Re: Automatically replacing part of text in a text label

Next by Date:
Accessing files from other folders.

Previous by thread:
Re: NSTableView behavior changes

Next by thread:
Re: Growl vs. CFUserNotification

Index(es):

Date
Thread