[PATCH notification] spec: Add badge-number hint
hadess at hadess.net
Mon Feb 16 10:18:49 PST 2015
On Mon, 2015-02-16 at 10:03 -0800, Jasper St. Pierre wrote:
> Jon had multiple reasons:
> 1. The main use for a counter like is "Unread Emails", a number that's
> particularly high for Jon that he didn't think it would be too useful.
> Notifications should be about the
About the? It's also very low for a number of people. I can also be
there to notify about the number of new podcasts episodes to read, the
number of unread articles in my offline reader app, the number of unread
messages in my chat application, or even the fact that there is an
> 2. It's hard to figure out what the number even means sometimes, or
> how to clear it. He showed me his iPhone which had some app which had
> a "2" badge, and there was seemingly no explanation for it. So we
> decided that we would always making it the number of unread
> notifications, and keep the UI for clearing that badge consistent.
It can be turned off in the Notifications settings on iOS, and so will
we be able to turn it off in GNOME.
> 3. It got stuck. Again, another app on his iPhone always listed that
> he had 1 unread message, when the app itself had nothing. It was
> definitely the number of unread messages, since it went up and down
> when he got new messages, but, again, there's a "1" that he could
> never clear because of an application bug.
Apps have bugs. Disable the badge, or remove the app then.
> Then, how do we implement this with the new notifications design in
> GNOME? I don't see a place for a badge in
I would show it on the app's icon, not in a separate notification.
Look for badge in this to see the equivalent iOS notification API:
Look for "badge".
> On Mon, Feb 16, 2015 at 9:44 AM, Bastien Nocera <hadess at hadess.net>
> On Mon, 2015-02-16 at 09:37 -0800, Jasper St. Pierre wrote:
> > Why and how?
> How what?
> > Note that not giving applications the badge number was an
> > design decision Jon, Cosimo and I made when we first
> > notifications.
> I'd like some explanations as to why this decision was made
> though. This
> is useful for a number of applications, and would be
> through the "Notifications" panel in GNOME (which we didn't
> have when
> this design decision was taken I guess).
> The server can also choose not to implement it (or cannot).
> > On Mon, Feb 16, 2015 at 9:21 AM, Bastien Nocera
> <hadess at hadess.net>
> > wrote:
> > As discussed during the Wayland meeting at FOSDEM
> > ---
> > docs/notification-spec.xml | 17 +++++++++++++++--
> > 1 file changed, 15 insertions(+), 2 deletions(-)
> > diff --git a/docs/notification-spec.xml
> > b/docs/notification-spec.xml
> > index fa1da0b..3bc0292 100644
> > --- a/docs/notification-spec.xml
> > +++ b/docs/notification-spec.xml
> > @@ -3,8 +3,8 @@
> > <article id="index">
> > <articleinfo>
> > <title>Desktop Notifications
> > - <releaseinfo>Version 1.2</releaseinfo>
> > - <date>28 October 2010</date>
> > + <releaseinfo>Version 1.3</releaseinfo>
> > + <date>16 February 2015</date>
> > <authorgroup>
> > <author>
> > <firstname>Mike</firstname>
> > @@ -674,6 +674,19 @@
> > <entry>>= 1.2</entry>
> > </row>
> > <row>
> > +
> > + <entry>INT32</entry>
> > + <entry>
> > + When set, a server can use it to show the
> > attached to
> > + the notification on top of the application
> > referenced by the
> > + "desktop-entry" hint.
> > + Note that servers can choose not to show
> the number,
> > either because
> > + they do not implement the capability, or in
> > to user
> > + configuration to suppress its display.
> > + </entry>
> > + <entry>>= 1.3</entry>
> > + </row>
> > + <row>
> > <entry><literal>"category"</literal></entry>
> > <entry>STRING</entry>
> > <entry>
> > _______________________________________________
> > xdg mailing list
> > xdg at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/xdg
> > --
> > Jasper
More information about the xdg