Re: Growl vs. CFUserNotification
Re: Growl vs. CFUserNotification
- Subject: Re: Growl vs. CFUserNotification
- From: Jean-Daniel Dupas <email@hidden>
- Date: Wed, 18 Mar 2009 09:26:27 +0100
Le 18 mars 09 à 05:45, Jerry Krinock a écrit :
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?
CFUserNotification is interactive. It returns user choices: which
button was pressed, if an eventual check box was checked, and it can
also contains a text field.
_______________________________________________
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