Hi Alex, I did mean object attribute vs relation. At this point in the discussion either of the three (object attribute, relation, method) is OK with me. Since the requirement does not seem to be an overwhelming one (from the input we have so far) perhaps adding an object attribute or relation is the most pragmatic solution.
Pete On 6/28/2011 5:05 AM, Alexander Surkov wrote: > Hi, Pete. > > I don't recall who exactly came up with new interface suggestion, > maybe it was me based on IA2 architecture in Gecko. > > Assuming you meant new relation rather than object attribute I believe > relations approach work as generic approach. Any getter property that > returns an object mapped well to relations mechanism, for example, > IATable2::caption property can be exposed by relations. The question > is when we want to introduce new method rather than reuse existing > generic-propose method. > > Thank you. > Alex. > > > On Fri, Jun 24, 2011 at 12:41 PM, Pete Brunet <[email protected] > <mailto:[email protected]>> wrote: > > Thanks Carolyn, > > Rich, When I read "accessibleDocument" I was thinking of the work > done by Cathy Laws back around 2005. I finally found that document at > > http://accessibility.linuxfoundation.org/a11yspecs/atspi/adoc/ADOC_ATK.html > Is this what you were thinking of? If so please start up a new > thread to discuss that. > > By the way, ATK does have AtkDocument, documented at > http://developer.gnome.org/atk/2.0/AtkDocument.html > with these methods: > atk_document_get_document_type > atk_document_get_document > atk_document_get_attribute_value > atk_document_set_attribute_value > atk_document_get_attributes > atk_document_get_locale > > From what I remember we didn't see a need for the first 4 > methods. We put the last two into the IAccessible2 interface so > at this point IA2 doesn't have an IAccessibleDocument interface. > > Jamie, In the bug at > https://bugzilla.mozilla.org/show_bug.cgi?id=617544 > you proposed solving the problem with a new relation or a new > accNavigate constant and in the new 1.3 document someone else, > perhaps Alex, has proposed a new interface with one method, > IAccessibleDocument::anchorTarget. (Perhaps that should have been > currentAnchor?) Could the problem be solved with a new object > attribute? > > Pete > > On 6/23/2011 10:51 AM, Carolyn MacLeod wrote: >> >> > You said you were looking at accessibleDocument. Please send >> me a link to what you are looking at. accessibleDocument is not >> part of IA2. >> >> Pete, the "next changes to IAccessible2" wiki has an >> "IAccessibleDocument" in >> it:_https://wiki.mozilla.org/Accessibility/IA2_1.3_ >> Perhaps it's a typo, and it was meant to be >> "IAccessibleHyperlink2" or maybe "IAccessibleHypertext2" ? >> >> Carolyn >> >> >> >> From: Pete Brunet <[email protected]> <mailto:[email protected]> >> To: IA2 List <[email protected]> >> <mailto:[email protected]> >> Date: 22/06/2011 01:40 PM >> Subject: Re: [Accessibility-ia2] next changes to IAccessible2 >> Sent by: [email protected] >> <mailto:[email protected]> >> >> >> ------------------------------------------------------------------------ >> >> >> >> >> >> On 6/22/2011 12:10 PM, Richard Schwerdtfeger wrote: >> >> >> >> Rich Schwerdtfeger >> CTO Accessibility Software Group >> _ >> [email protected]_ >> <mailto:[email protected]>wrote >> on 06/22/2011 11:16:41 AM: >> >> > From: Pete Brunet _<[email protected]>_ <mailto:[email protected]> >> > To: IA2 List _<[email protected]>_ >> <mailto:[email protected]> >> > Date: 06/22/2011 11:19 AM >> > Subject: Re: [Accessibility-ia2] next changes to IAccessible2 >> > Sent by: [email protected]_ >> <mailto:[email protected]> >> > >> > >> > On 6/22/2011 8:27 AM, Richard Schwerdtfeger wrote: >> > Pete, >> > >> > I am looking at accessibleDocument. Should we not do more than >> that >> > for a document interface? Should we also have features to collect >> > and access specific objects with a specific element type - >> filtering >> > mechanisms? >> > Hi Rich, It's been a long time since I looked at >> accessibleDocument. >> > (It's not part of IA2.) I couldn't find a link in my archives. >> > Please send it. Would that discussion be better held on the parent >> > LF a11y list at [email protected]_ >> <mailto:[email protected]>? That >> > will also be of interest to the Linux a11y architects. >> > >> I have no idea. I just found it odd that we would add only one >> method for a document. >> >> You said you were looking at accessibleDocument. Please send me >> a link to what you are looking at. accessibleDocument is not >> part of IA2. For Symphony documents access is provided via >> IAccessibleText, IAccessibleHyperText, and IAccessibleHyperlink. >> >> >> > Note: I am in favor of not unnecessarily growing the API. API >> > changes cause a lot of churn. However, with the FCC adopting >> > creating new laws based on the 21st Century Communication and >> Video >> > act there is a need for infrastructure to better support the >> HTML 5 >> > changes Silvia is working on to support video and audio. >> > >> > I am looking at the notification mechanism for media >> > MEDIA_TEXT_QUEUE_CHANGE. Would it be better to have a callback >> > registry for ATs similar to what we did in Java? I am concerned >> > about potential OS scheduling issues caused by posting events >> to the >> > message queue. >> > We've talked about adding something to get around the >> limitations of >> > WinEvent, primarily the lack of an event payload so out of process >> > AT don't have to use (and possibly get stale data) on a following >> > call fetching event data. It's not become enough of an issue that >> > the group has pushed that change through though. >> > >> > For in process AT the callback happens on the same thread that >> fires >> > the event. Jamie might be able to comment on what problems there >> > might be for out of process AT when handing a cue change event. >> > >> >> I think the difference here is we are trying to keep the video >> and audio descriptions in synch. That adds an additional level of >> concern for me. I will look to see what Jamie says. Descriptions >> could be quite long. >> > >> > >> > >> > Rich Schwerdtfeger >> > CTO Accessibility Software Group >> > >> > [image removed] Pete Brunet ---06/06/2011 11:12:32 PM---Hi all, >> > Please take a look at this and provide your feedback: >> _https://_ <https:///> >> > wiki.mozilla.org/Accessibility >> <http://wiki.mozilla.org/Accessibility> >> > >> > From: Pete Brunet _<[email protected]>_ <mailto:[email protected]> >> > To: IA2 List _<[email protected]>_ >> <mailto:[email protected]> >> > Date: 06/06/2011 11:12 PM >> > Subject: Re: [Accessibility-ia2] next changes to IAccessible2 >> > Sent by: [email protected]_ >> <mailto:[email protected]> >> > >> > >> > >> > Hi all, Please take a look at this and provide your feedback: >> > >> > _https://wiki.mozilla.org/Accessibility/IA2_1.3_ >> > >> > Thanks, Pete >> > -- >> > Pete Brunet >> > >> > a11ysoft - Accessibility Architecture and Development >> > (512) 238-6967 (work), (512) 689-4155 (cell) >> > Skype: pete.brunet >> > IM: ptbrunet (AOL, Google), [email protected]_ >> <mailto:[email protected]>(MSN) >> > _http://www.a11ysoft.com/about/_ >> > Ionosphere: WS4G >> > >> > On 3/11/2011 11:10 PM, Alexander Surkov wrote: >> > Hi, Jamie. I missed Mick suggestion on the list. It's sounds >> > reasonable and I agree we should try it before getting new API for >> > this since the issue is mostly about events. >> > >> > Thank you. >> > Alex. >> > >> > >> > On Sat, Mar 12, 2011 at 11:43 AM, James Teh >> _<[email protected]>_ <mailto:[email protected]>wrote: >> > Hi. >> > >> > Nice work; good to get the discussion going. :) >> > >> > I still don't see a need for this registry API. Why not just use >> > IsWinEventHookInstalled(), as Mick suggested on the IA2 list? >> > >> > Thanks. >> > >> > Jamie >> > >> > >> > On 12/03/2011 3:48 AM, Alexander Surkov wrote: >> > Hi. >> > >> > I gathered ideas into one doc - >> > _https://wiki.mozilla.org/Accessibility/IA2_1.3_. Please give >> feedback >> > here and feel free to edit the wiki. >> > >> > Thank you. >> > Alex. >> > >> > -- >> > James Teh >> > Vice President, Developer >> > NV Access Inc, ABN 61773362390 >> > Email: [email protected]_ <mailto:[email protected]> >> > Web site: _http://www.nvaccess.org/_ >> > _______________________________________________ >> > Accessibility-ia2 mailing list >> > [email protected]_ >> <mailto:[email protected]> >> > >> _https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2_ >> > _______________________________________________ >> > Accessibility-ia2 mailing list >> > [email protected]_ >> <mailto:[email protected]> >> > >> _https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2_ >> >> >> >> -- * >> Pete Brunet* >> >> a11ysoft - Accessibility Architecture and Development >> (512) 689-4155 (cell) >> Skype: pete.brunet >> IM: ptbrunet (AOL, Google), [email protected]_ >> <mailto:[email protected]>(MSN)_ >> __http://www.a11ysoft.com/about/_ >> Ionosphere: WS4G _______________________________________________ >> Accessibility-ia2 mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 >> > > _______________________________________________ > Accessibility-ia2 mailing list > [email protected] > <mailto:[email protected]> > https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 > >
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
