<div class="gmail_quote">2009/6/13 Aurélien Gâteau <span dir="ltr"><<a href="mailto:aurelien.gateau@canonical.com">aurelien.gateau@canonical.com</a>></span><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">Brian J. Tarricone wrote:<br>
> On 06/13/2009 02:18 PM, Aurélien Gâteau wrote:<br>
>> Brian J. Tarricone wrote:<br>
>>> 1. Passive vs. active notifications. I recall that notify-osd<br>
>>> unilaterally decided that the 'actions' bit of the spec was Bad[tm] and<br>
>>> that notifications should be entirely passive and not accept input.<br>
>> I would rather not start a discussion on this subject: it has been<br>
>> debated to death and people won't change their mind.<br>
><br>
> That's rather closed-minded. But I suppose if Canonical wants to go<br>
> their own way and ignore community consensus, it's free to do so.<br>
<br>
</div>What I wanted to say is that I read a lot of discussions on that issue<br>
and I learned nothing positive ever come out of those, so I'd rather<br>
talk about icons, markup and other things instead.<br>
<br>
The spec says actions are optional and I don't think Canonical wants to<br>
have this changed.<br>
<br>
(Also note that I have personally nothing to do with the choice to go<br>
action-less, I was not even working for Canonical at the time of this<br>
decision)<br>
<font color="#888888"><br></font></blockquote></div><br>A little bit of background on this.<br><br>The intent originally was to make it optional so that a daemon could intercept the messages and log to console or to a log file, which wouldn't allow for feedback. The original notification-daemon was actually built this way, to be able to be used in a graphical or console manner.<br>
<br>We intended for all graphical implementations to support actions. The spec does not explicitly say this, which is an oversight. At the time there was just libnotify and notification-daemon, so it didn't really matter. notification-daemon was considered the reference implementation that provided the minimum amount of functionality a daemon should implement.<br>
<br>If I thought we'd face an issue down the road where actions would be removed from all apps in a distro and the new notification-daemon replacement would not support them, I would have made this *VERY* clear in the spec from the beginning. I think it's harmful to do this.<br>
<br>Christian<br><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>
<br><br>