Notification spec issue: Ability to assign an icon *and* an image to a notification

Jeff Mitchell mitchell at
Thu Jun 25 13:41:15 PDT 2009

Brian J. Tarricone wrote:
>> -- if you developed based solely on the interfaces exposed on
>> dbus instead of an actual spec/"API", then that's not dissimilar to
>> making use of undocumented methods you found in libraries via "nm" and
>> then complaining when the library maintainer yanks them away.  When I
>> had to make use of HAL, I looked at the spec, I didn't just look at the
>> output of "lshal -lt"...
> Bad analogy and not at all representative as to what I -- and others -- 
> did.  Who's talking about being dishonest, mmm?

I didn't say that this is what you did.  I said that *if* that is what
you did, then it would absolutely be your fault.  (Now that you've
stated what it is you did: it's still your fault.)

> Anyway, I'm kinda getting tired of this discussion.  It seems clear to 
> me that I'm not really getting my point across

No, your point comes across loud and clear.

> but my own) and I'm not going to change anyone's mind here

Bingo.  At least, not with your current arguments/points.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
Url : 

More information about the xdg mailing list