[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ayatana] Audial notifications.
- To: Jeremy Nickurak <jeremy@xxxxxxxxxxx>
- Subject: Re: [Ayatana] Audial notifications.
- From: Dylan McCall <dylanmccall@xxxxxxxxx>
- Date: Sat, 25 Sep 2010 09:28:22 -0700
- Cc: Ayatana List <ayatana@xxxxxxxxxxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=+CeWCGezyK3VSfb5bsc47k3xc+8YoqSS5mvutWyqleU=; b=Uuq/nG39TUDReyNIZL8gnQ+1H/9HYb5oUR4ZCxCevJpvG9Qq2Vt4whD/nfXla5gU+4 9MIVzTS7VSepPszmQhP2Z7WZn8+yj+U9Y5BuDd6x+Z9rJpkbb40DbdmyYrUjLW/JfOaQ aWHH1XF6xQpvGIYrBn9GH0OQ+x5a/rIKkhoKA=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=Zz46WI5eDkWEaqYoHrEOVpXpriaeBbrzUi7NKFKrGn0idBCsBr6k4O+Xmt7OHVvV3N kmpj4Mp9q9E1I2PlA+vNYSOR09c6NhitrHDZ52NkyODDE5Ck5mOdn24dwf17W3BG2ljA A4jKp8ymytZPotDebHuvH96tjuyRKVPmNuL/w=
- In-reply-to: <AANLkTim_VLexa5ZsoFVdstuvOR26qzt0C8VZCrA=AQg_@mail.gmail.com>
- List-archive: <http://lists.launchpad.net/ayatana>
- List-help: <https://help.launchpad.net/ListHelp>
- List-id: <ayatana.lists.launchpad.net>
- List-owner: <https://launchpad.net/~ayatana>
- List-post: <mailto:ayatana@lists.launchpad.net>
- List-subscribe: <https://launchpad.net/~ayatana>
- List-unsubscribe: <https://launchpad.net/~ayatana>
- References: <AANLkTi=xvpMMGmt9N1K-aGYYYYqOSo8vvqwjfngiqOJ2@mail.gmail.com> <AANLkTi=r7u+Y=vtMwNrXGdLgFAGSKPyteWXc5zOsbMPj@mail.gmail.com> <1285428946.23532.4.camel@u0> <AANLkTim_VLexa5ZsoFVdstuvOR26qzt0C8VZCrA=AQg_@mail.gmail.com>
> Maybe. And people always have the option of playing a sound via pulseaudio
> directly, or with libcanberra.
>
> I would however argue that 99% of the time, if you want an audio
> *notification*, you probably want a messaging menu item, *AND* a notify-osd
> notification too.
>
> Like notify-osd bubbles, audio notifications are by definition "ethereal",
> and disappear as soon as they're gone. If something happened that's so
> important that we need a sound to tell the user... there should probably be
> an indication of what happened that's there until they dismiss it (ie, the
> messaging menu). This is especially true if you're playing audio
> notifications while the user is away from the computer, and then comes back.
Attaching a sound hint to notifications is in notify-osd's
specification (and the desktop notifications spec).
I put a patch implementing the feature here:
https://bugs.edge.launchpad.net/notify-osd/+bug/549900
As for tying together libnotify and the message indicator under Yet
Another library, I'm pretty worried about that idea. It would split us
further from upstreams (in a wacky, tangled way), increasing the
significant load of patches being applied and maintained within
Ubuntu.
The notifications spec (as in libnotify) is pretty expressive, and I
get the feeling that it's completely wrong that all the
implementations use a single trick for presentation (a bubble),
leaving other methods of presenting that same information to other
specifications entirely. It's like buying an assault vehicle to get
the groceries.
Dylan