<br><br><div class="gmail_quote">On Sat, Jun 13, 2009 at 3:08 PM, Brian J. Tarricone <span dir="ltr"><<a href="mailto:bjt23@cornell.edu">bjt23@cornell.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 06/13/2009 02:26 PM, Christian Hammond wrote:<br>
> They know my stance on this one. Upstream libnotify and notification-daemon<br>
> will always support actions.<br>
<br>
</div>Might be a little OT for xdg-list, but: would you be interested in<br>
adding support to libnotify (or accepting a patch) to query for the<br>
'actions' capability, and if the daemon doesn't support it,<br>
transparently convert notifications with actions into dialog boxes (and<br>
proxy GtkDialog::response to NotifyNotification::action-invoked and<br>
::closed appropriately)? Would be great to avoid having to write<br>
special-case code in apps to handle daemons that doesn't support<br>
actions, and I'd bet the Ubuntu guys would be happier to not have to<br>
support actions at all for compatibility.</blockquote><div><br>I'll definitely support querying for the actions capability. There's a patch that was submitted (which I'll try to get in soon) that checks for individual capabilities.<br>
<br>I would support libnotify popping up a dialog when actions aren't supported, but I'm not ready to do that, specifically because I'm still against Ubuntu's notification-daemon replacement not supporting actions. As you'll see in another e-mail I just sent, the original intention was for graphical daemons (notification-daemon being the only one in existence when we wrote the spec) to support actions, and console/file loggers (something we considered building early on) to not support actions.<br>
<br>Christian <br></div></div><br clear="all">-- <br>Christian Hammond - <a href="mailto:chipx86@chipx86.com">chipx86@chipx86.com</a><br>Review Board - <a href="http://www.review-board.org">http://www.review-board.org</a><br>
VMware, Inc. - <a href="http://www.vmware.com">http://www.vmware.com</a><br>