comments on StatusNotifier spec

2010-01-18 Thread Dan Winship
(So rereading this, it comes across as kinda harsh, but it wasn't supposed to be, so just add a :-) to the end of every line or something. :-) This specification does not define what the aspect of the Noticication Items will be, this is strictly implementation specific. What does aspect mean?

Re: comments on StatusNotifier spec

2010-01-18 Thread Aaron J. Seigo
On January 18, 2010, Dan Winship wrote: StatusNotifierHost When I first saw this term in the spec I thought it was talking about having a status icon on one machine and a tray on a different machine. for all that the status item cares, it could be. Maybe this is just because I write lots

Re: comments on StatusNotifier spec

2010-01-18 Thread Aaron J. Seigo
On January 18, 2010, you wrote: On 01/18/2010 03:12 PM, Aaron J. Seigo wrote: Also, you need to give *some* indication of what this is for. Eg, currently it could mean anything from Please raise the indicated window if the user clicks on the status item to Please hide the indicated window

Re: comments on StatusNotifier spec

2010-01-18 Thread Aaron J. Seigo
On January 18, 2010, Aaron J. Seigo wrote: On January 18, 2010, you wrote: On 01/18/2010 03:12 PM, Aaron J. Seigo wrote: Also, you need to give *some* indication of what this is for. Eg, currently it could mean anything from Please raise the indicated window if the user clicks on the

Re: comments on StatusNotifier spec

2010-01-18 Thread Matthias Clasen
I must say I am a bit taken aback by your responses here. Dan's mail made me look at the spec for the first time, and I have to say he is entirely right in his criticism. The spec is full of awkward naming (StatusNotifierHost, ServiceRegistered, etc), internally inconsistent (e.g there's a

Re: comments on StatusNotifier spec

2010-01-18 Thread Matthias Clasen
On Mon, 2010-01-18 at 18:17 -0800, Aaron J. Seigo wrote: On January 18, 2010, Matthias Clasen wrote: The spec is full of awkward naming (StatusNotifierHost, ServiceRegistered, etc), as noted in my replies, i agree that ServiceRegistered should/could be named better. the quibble on

Re: comments on StatusNotifier spec

2010-01-18 Thread Aaron J. Seigo
On January 18, 2010, you wrote: On Mon, 2010-01-18 at 18:17 -0800, Aaron J. Seigo wrote: On January 18, 2010, Matthias Clasen wrote: The spec is full of awkward naming (StatusNotifierHost, ServiceRegistered, etc), as noted in my replies, i agree that ServiceRegistered should/could be