RE: [g-a-devel] AtkInterfaces for gnome-about

[Marc Mulcahy <marc mulcahy sun com>]

Hi,

I'll give this a try.  Let me know if this makes sense...

What would typically happen, in the case of a screen reader, would be that 
when an object within a dialog box gets the focus, some more sophistocated 
logic is invoked.  For example, in gnome-about, when the OK button gets the 
focus, which sseems to be the case when the GnomeAbout widget gets 
displayed, the screen reader would traverse up the higherarky to find the 
Dialog box itself.  Once found, it would then traverse through the children 
of the dialog looking for text to speak.  In the case of an accessible 
object representing the contributors, it would be found and the list of 
contributors would be spoken.

Maybe this is a moot point, but why not convert the contributors list to a 
GtkTextview as the authors and other elements have been.

Marc

At 10:50 AM 2/18/2002 +0000, Padraig O'Briain wrote:

> >
> > Padraig,
> >
> > >
> > > I have spent some time figuring out why I could not
> > > manipulate gnome-about using
> > > the keyboard. I have logged bug 71832 and proposed a patch.
> > >
> > I too agree on doing away with the glittering stuff (sparkles:)
> >
> > >
> > > The AT would get to the atk object by traversing the tree of
> > > accessible objects.
> > > One would call atk_object_accessible_child() on its parent.
> > > This will cause
> > > gail_container_ref_child() to be called which calls
> > > gtk-widget_get_accessible().
> > > If gtk_widget_get_accessible() returns the correct type of
> > > object, see above,
> > > then things should work.
> > >
>
> Marc or Bill would speak with more authority than me on this point.
> However, there are widgets which will not receive focus which an AT will 
> need to
> report on.
>
> Padraig
>
> > Should an AT traverse the whole tree (starting from root) and cache the
> > entire (ATK) info about the app? I would assume that the atk object
> > would be created only if it's required by the AT (like for e.g., create
> > atk object only when the focus moves to a widget via mouse/keyboard).
> >
> > Can you please clarify on this?
> >
> > Cheers,
> > Mukund.
> >
> >
> >
> >
> > begin 666 Wipro_Disclaimer.txt
> > M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BI$:7-C;&%I;65R*BHJ*BHJ*BHJ
> > M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ"B @(" @( T*#0H-"DEN9F]R
> > M;6%T:6]N(&-O;G1A:6YE9"!I;B!T:&ES($4M34%)3"!B96EN9R!P<F]P<FEE
> > M=&%R>2!T;R!7:7!R;R!,:6UI=&5D#0II<R G<')I=FEL96=E9"<@86YD("=C
> > M;VYF:61E;G1I86PG(&%N9"!I;G1E;F1E9"!F;W(@=7-E(&]N;'D 8GD@=&AE
> > M#0II;F1I=FED=6%L(&]R(&5N=&ET>2!T;R!W:&EC:"!I="!I<R!A9&1R97-S
> > M960N(%EO=2!A<F4@;F]T:69I960 =&AA="!A;GD-"G5S92P 8V]P>6EN9R!O
> > M<B!D:7-S96UI;F%T:6]N(&]F('1H92!I;F9O<FUA=&EO;B!C;VYT86EN960@
> > M:6X =&AE($4M34%)3 T*:6X 86YY(&UA;FYE<B!W:&%T<V]E=F5R(&ES('-T
> > M<FEC=&QY('!R;VAI8FET960N"@T*#0H-"B J*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ
> > M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ
> > &*BHJ* T*
> > end
> >
> > _______________________________________________
> > Gnome-accessibility-devel mailing list
> > Gnome-accessibility-devel gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
>
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel