On Thu, Feb 11, 2010 at 11:10 AM, Robert O'Callahan <robert@ocallahan.org>wrote: > We ran into this issue when mapping our own browser notifications to > platform notification APIs. For ambient notifications, you can't rely on the > user being able to click on the notification, because the notification might > time out and disappear on its own before the user has had a chance to react, > so there always has to be another way for the user to get the information > and perform the action. So NotifyOSD not supporting actions is an issue of > convenience, not functionality. > > So then, if the NotifyOSD designers think their users don't need that > convenience, that's their call. A generic API can offer support for actions > with the understanding that in some cases users won't be able to use them. > Er, ignore that entire message. Sorry! Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
Received on Wednesday, 10 February 2010 22:22:41 UTC