New property proposal for StatusNotifierItem protocol: Label

[Aurélien Gâteau]

On 10/08/2010 21:26, Aaron J. Seigo wrote:

> this could be a similar thing: in this "non-standard collection of key/value
> pairs", Unity (or whatever it really is in this case :) could go looking for
>   an "IconText" key (or whatever it would get named) and use that.
>
> it would mean that there would be no need to expand the spec itself while
> allowing us to all experiment a bit more freely with it. all without
> endangering the future quality of the API and burden existing
>   visualizations.
>
> and if i am proven horribly, wonderfully wrong and the label text is shown
> to be a purely awesome idea full of rainbows and unicornsparkles then we
> could 'promote' that key/value pair into the spec as either a document item
> in the key/value property, or as a full fledged named property in the API
>   itself
>
> what does everyone think? (and by "everyone" i mean mostly Marco, Ted and
>   Aurelian, though others are welcome to weight in, of course :)

(sorry for the latency, I am supposed to be away until Monday)

This idea sounds like a reasonable middle ground to me. Ted version is 
probably even simpler. We can state in the protocol that vendor specific 
properties can be created, as long as they are named something like 
X<Vendor><PropertyName>.

Aurélien