Re: [g-a-devel] Fine-tuning event listeners?

[Mike Gorse <mgorse alum wpi edu>]

Hi Joanie,

Thanks for the proposal.

I think that doing something along these lines makes sense and that it 
should be extensible (ie, we should have the ability to define new 
properties to filter on in future versions of AT-SPI without breaking the 
protocol).  This seems similar to a comment that you made in Spain, that 
it would be useful if applications sent the data that Orca needed to begin 
with so that AT-SPI wouldn't need to make queries over the wire for the 
information after seeing an event.  So I think that something similar 
would be useful to allow an AT to specify the type of data that it is 
likely to want from applications when events are sent.  This could be 
added into registerEventListener, and events could be sent with one of 
their fields being a dictionary of properties that the AT requested for 
that type of event.

-Mike

On Sun, 23 Jan 2011, Joanmarie Diggs wrote:

> Hey guys.
>
> As I understand it, when an AT registers a listener for a given AT-SPI event, 
> there is no way to specify things like:
>
> * The object role(s) the AT cares about w.r.t. that event type
> * The app(s)/toolkit(s) the AT cares about w.r.t. that event type
>
> For instance, if Orca cares about object:children-changed events from OOo for 
> tables, Orca is then forced to listen to -- and subsequently filter out -- 
> all object:children-changed events that any running accessible app happens to 
> emit for any type of accessible.
>
> I don't have any good ideas about how to implement fine-tuning for event 
> listeners. But since we're discussing Atk3/AT-SPI3 -- or whatever Piñeiro is 
> calling it ;-) ;-) -- I figured I'd toss it out there for consideration.
>
> Thanks all! Take care.
> --joanie
> _______________________________________________
> gnome-accessibility-devel mailing list
> gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel