On Sun, 2009-10-11 at 07:17 +0100, Mark Shuttleworth
> None of those fit in the MI, imo.
>
> > My thinking of good examples:
> > Your download is complete: Pick it up [Here]
> > Your print Job failed. Go [Here] to resend to printer.
> > Updates are available. Go [Here] to install.
> >
> Yuck
Jim Rorie wrote:
> On Fri, 2009-10-09 at 18:39 +0100, Mark Shuttleworth wrote:
>
>> To the extent that the things which need responding to really are
>> messages, this is appropriate.
>>
>
> What do you feel would be an example of something that wasn't
> appropriate?
>
> My thinking of q
On Fri, 2009-10-09 at 18:39 +0100, Mark Shuttleworth wrote:
> To the extent that the things which need responding to really are
> messages, this is appropriate.
What do you feel would be an example of something that wasn't
appropriate?
My thinking of questionable examples:
App crashes. Dialo
Sorry for taking ages to catch up on this thread. I've snipped a long
piece where Jim describes the MI as a generic "respond to notifications"
mechanism.
Jim Rorie wrote:
> Pros: This would provide interactivity through lib notify and quiet a chief
> complaint. Users would not be challenged to r
On Friday 11,September,2009 04:52 PM, David Barth wrote:
> > It is was not on the table for Karmic, that is, Mozilla had reservations
> > last year about the non-interactivity of n-osd notifications and I think
> > they prefer to see how the rest of the community reacts to our change
> > before rec
On Fri, 11 Sep 2009 19:18:34 +0800 Chow Loong Jin
wrote:
> ... how
>about making the actions optional? For example, don't show actions for
>notify-osd users (where actions aren't supported), but show actions for
>notification-daemon users, much like most of the other applications are
doing.
...
On Friday 11,September,2009 04:52 PM, David Barth wrote:
> It is was not on the table for Karmic, that is, Mozilla had reservations
> last year about the non-interactivity of n-osd notifications and I think
> they prefer to see how the rest of the community reacts to our change
> before reconsideri
mac_v wrote:
> From: David Barth
> To: Steve Dodier
> Cc: ayatana@lists.launchpad.net
> Sent: Wednesday, 9 September, 2009 1:59:44 PM
> Subject: Re: [Ayatana] Notification consistency
>
> Steve Dodier wrote:
>
>> +1 too, but it'll require Mozilla to n
From: David Barth
To: Steve Dodier
Cc: ayatana@lists.launchpad.net
Sent: Wednesday, 9 September, 2009 1:59:44 PM
Subject: Re: [Ayatana] Notification consistency
Steve Dodier wrote:
> +1 too, but it'll require Mozilla to natively support libnotify for their
> Linux client. I'm ac
Steve Dodier wrote:
> +1 too, but it'll require Mozilla to natively support libnotify for their
> Linux client. I'm actually surprised it's still not the case...
>
Mozilla has support for libnotify in their trunk branch, but they don't
enable that build option by default. Now that the protocol h
2009/9/7 Mike Rooney
> On Mon, Sep 7, 2009 at 6:04 AM, Steve Dodier wrote:
> >> > Also I was thinking that firefox should use notify-osd to display when
> a
> >> > download is finished. I know that an addon for firefox exists so why
> not
> >> > use it by default?
> >
> > +1 too, but it'll requir
On Mon, Sep 7, 2009 at 6:04 AM, Steve Dodier wrote:
>> > Also I was thinking that firefox should use notify-osd to display when a
>> > download is finished. I know that an addon for firefox exists so why not
>> > use it by default?
>
> +1 too, but it'll require Mozilla to natively support libnotify
Hello,
> > I was thinking that this info could be displayed in
> > notify-osd too.
>
I have actually tried to do it. It's not possible because the gtk status
icon's tooltip-query signal doesn't behave as expected.
> > Also I was thinking that firefox should use notify-osd to display when a
>
2009/9/7 Shane Fagan :
> I was thinking that this info could be displayed in
> notify-osd too.
Please don't, how it's now I can control exactly how long I want to
see the information, and the tooltip is placed exactly below where I
have my mouse cursor (so I can read the information, decide I want
14 matches
Mail list logo