unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mike Kazantsev <mk.fraggod@gmail.com>
To: emacs-devel@gnu.org
Cc: Julien Danjou <julien@danjou.info>
Subject: Re: [PATCH] notifications.el: fixed image-data and image-path hints passing
Date: Mon, 7 Nov 2011 14:35:32 +0600	[thread overview]
Message-ID: <20111107143532.2892852e@malediction> (raw)
In-Reply-To: <20111107142911.1822efa2@malediction>

[-- Attachment #1: Type: text/plain, Size: 2104 bytes --]

On Mon, 7 Nov 2011 14:29:11 +0600
Mike Kazantsev <mk.fraggod@gmail.com> wrote:

> On Mon, 7 Nov 2011 14:22:30 +0600
> Mike Kazantsev <mk.fraggod@gmail.com> wrote:
> 
> > 
> > Good day,
> > 
> > Before the patch, hints were passed as "image_path" and "image_data",
> > which is incorrect, as Desktop Notifications Specification v1.2 clearly
> > states:
> > 
> >   The icon is defined by the "app_icon" parameter. The image can be
> >   defined by the "image-path", the "image-data" hint or the deprecated
> >   "icon_data" hint.
> > 
> > Most common (by far) implementation of spec - libnotify - seem to pass
> > them as described in spec as well, so current behavior looks like a bug.
> > 
> 
> Actually looking at previous spec versions (which can be found on
> http://www.galago-project.org/specs/notification/), there seemed to be
> an "icon_data" hint in 0.9, but not "icon_path", so I can guess that's
> where these came from.
> 
> Mentioned specs seem to be fairly obsolete now, and even if they
> should be supported, there doesn't seem to be any excuse to pass
> "icon_path".
> 

Hmm... and looking further at 1.1, which is mentioned a bit below in
the code, and even set as "notifications-specification-version", I see
that current implementation is actually correct.

Terribly sorry for the confusion and the noise, should've checked the
specs more closely.

Desktop Notifications Specification 1.1:
 http://people.gnome.org/~mccann/docs/notification-spec/notification-spec-1.1.html

P.S. Link to galago-project.org at the top of the module seem to be
bogus though - specs there only cover versions up to 0.9, but I guess
it's not worth a separate fix.


> 
> > Patch to pass "image-path" and "image-data" hints - as per spec - is
> > attached below.
> > 
> > Desktop Notifications Specification:
> > 
> >   http://developer.gnome.org/notification-spec/#icons-and-images
> >   http://people.gnome.org/~mccann/docs/notification-spec/notification-spec-latest.html#icons-and-images
> > 
> ...
> 
> 


-- 
Mike Kazantsev // fraggod.net

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2011-11-07  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07  8:22 [PATCH] notifications.el: fixed image-data and image-path hints passing Mike Kazantsev
2011-11-07  8:29 ` Mike Kazantsev
2011-11-07  8:35   ` Mike Kazantsev [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111107143532.2892852e@malediction \
    --to=mk.fraggod@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=julien@danjou.info \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).