Re: SNI Additions Summary

2011-02-17 Thread Ted Gould
On Wed, 2011-02-16 at 22:47 +0100, Marco Martin wrote: > On Wednesday 16 February 2011, you wrote: > > > > Oh, I thought you meant to use "AccessibleDescription" as a suffix. > > > > I guess my concern with not having two is that it means when there is a > > state change signal we've got to do a

SNI Additions Summary

2011-02-11 Thread Ted Gould
Okay, I think we're done discussing, so let me try and summarize to make sure I understand (and everyone can correct me if not :) * Adding a field "X-KDE-StatusNotifierItems" to track the IDs of items in the desktop files was agreed upon. Other solutions were talked about,

[Fwd: Re: [Fwd: Re: New properties for StatusNotifierItem: Accessible Label (1/3)]]

2011-02-09 Thread Ted Gould
tthew Paul Thomas -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ted Gould wrote on 08/02/11 20:23: >... > Do you have thoughts on this from the a11y perspective? They want to > use the title of the tooltip for the accessible label. It seems to me > that would be sub-optimal, but if

Re: New properties for StatusNotifierItem: (Not|Only)ShowIn (2/3)

2011-02-04 Thread Ted Gould
t my concern is more that they have a way to explicitly provide which visualization that they're over-optimizing for. --Ted On Thu, 2011-02-03 at 22:01 -0800, Aaron J. Seigo wrote: > On Thursday, February 3, 2011, Ted Gould wrote: > > On Thu, 2011-02-03 at 09:19 -0800,

Re: New properties for StatusNotifierItem: (Not|Only)ShowIn (2/3)

2011-02-03 Thread Ted Gould
people who want to tweak specific visualizations with known short term results should be possible. On Thu, 2011-02-03 at 10:43 -0800, Aaron J. Seigo wrote: > On Thursday, February 3, 2011, Ted Gould wrote: > > people wanting different menus on the panel vs. on the launcher. > >

Re: New properties for StatusNotifierItem: Accessible Label (1/3)

2011-02-03 Thread Ted Gould
On Thu, 2011-02-03 at 16:24 +0100, Sebastian Kügler wrote: > On the other hand, it requires application developers to add another > string in their code to all UI elements -- something which might be > easily forgotten by those that don't care a lot about a11y (I fear > that this applies to a lot o

Re: New properties for StatusNotifierItem: Desktop Key (3/3)

2011-02-03 Thread Ted Gould
On Thu, 2011-02-03 at 14:45 +0100, Marco Martin wrote: > On Thursday 03 February 2011, Ted Gould wrote: > > We'd like to suggest an additional key for .desktop files that lists the > > IDs of Status Notifier Items that an application exports. This will > > allow us to b

Re: New properties for StatusNotifierItem: (Not|Only)ShowIn (2/3)

2011-02-03 Thread Ted Gould
On Thu, 2011-02-03 at 14:41 +0100, Marco Martin wrote: > On Thursday 03 February 2011, Ted Gould wrote: > > We also started to use some of the application indicators from > > applications in the launcher on the left side of the screen. We use the > > application indicator

Re: New properties for StatusNotifierItem: Accessible Label (1/3)

2011-02-03 Thread Ted Gould
On Thu, 2011-02-03 at 14:37 +0100, Marco Martin wrote: > On Thursday 03 February 2011, Ted Gould wrote: > > One of the projects we're doing is to try and make Unity more > > accessible. To that end we'd like to add properties to add accessible > > labels for t

Re: New properties for StatusNotifierItem (0/3)

2011-02-03 Thread Ted Gould
On Thu, 2011-02-03 at 14:27 +0100, Marco Martin wrote: > On Thursday 03 February 2011, Ted Gould wrote: > > I'd like to propose some new properties to be added to the SNI interface > > for a couple of projects in the Application Indicator framework that we > > have over

New properties for StatusNotifierItem: Desktop Key (3/3)

2011-02-03 Thread Ted Gould
Hello, For an intro see the mail with the (0/3) in the subject line. We'd like to suggest an additional key for .desktop files that lists the IDs of Status Notifier Items that an application exports. This will allow us to better match SNI items when we are using them as quicklists, as errors are

New properties for StatusNotifierItem: (Not|Only)ShowIn (2/3)

2011-02-03 Thread Ted Gould
Hello, For an intro see the mail with the (0/3) in the subject line. We also started to use some of the application indicators from applications in the launcher on the left side of the screen. We use the application indicator to provide additional menus for the launcher which we call a quick lis

New properties for StatusNotifierItem (0/3)

2011-02-03 Thread Ted Gould
Hello, I'd like to propose some new properties to be added to the SNI interface for a couple of projects in the Application Indicator framework that we have over here. We'd love it if you guys would consider adopting them in the base spec. Also, if you have comments on how to make them better I

New properties for StatusNotifierItem: Accessible Label (1/3)

2011-02-03 Thread Ted Gould
Hello, For an intro see the mail with the (0/3) in the subject line. One of the projects we're doing is to try and make Unity more accessible. To that end we'd like to add properties to add accessible labels for the icons that could be given to screen readers. We're planning on issuing warnings

Re: New property proposal for StatusNotifierItem protocol: Label

2010-08-10 Thread Ted Gould
On Tue, 2010-08-10 at 12:26 -0700, Aaron J. Seigo wrote: > On August 10, 2010, Ted Gould wrote: > > I think that's were we're coming at this from different positions, we > > don't have another API for it. > > ah, i see. that is indeed problematic. so i&#x

Re: New property proposal for StatusNotifierItem protocol: Label

2010-08-10 Thread Ted Gould
(I just snipped everything else, because I agree this is the heart of the matter) On Tue, 2010-08-10 at 11:21 -0700, Aaron J. Seigo wrote: > On August 10, 2010, Ted Gould wrote: > > And to overlay text is also non-ideal because making > > the text readable > requires basically

Re: New property proposal for StatusNotifierItem protocol: Label

2010-08-10 Thread Ted Gould
On Tue, 2010-08-10 at 09:40 -0700, Aaron J. Seigo wrote: > i really think this is one of those places where we should draw a line in > the sand and say "beyond this point, text doesn't happen, sorry." getting > rid of textual data in the primary display of these items is a good thing, > not a bad t