[Accessibility-ia2] Relations

[Carolyn MacLeod]

I am wrong about deprecating nRelations if "relation" is gone, because the 
client is allocating the array and they would want to use the correct 
amount of memory.
(Sorry about that - I tend to view things from the server's point of view 
<g>).

So if IAccessibleRelationships was ever added, it would need nRelations as 
well, because "It is considered a best practice for the client to allocate 
and free the arrays." (Why is that, anyhow?)

Carolyn




From:
Carolyn MacLeod/Ottawa/IBM at IBMCA
To:
pete at a11ysoft.com
Cc:
accessibility-ia2-bounces at lists.linuxfoundation.org, IA2 List 
<Accessibility-ia2 at lists.freestandards.org>
Date:
22/10/2009 11:07 AM
Subject:
Re: [Accessibility-ia2] Relations
Sent by:
accessibility-ia2-bounces at lists.linuxfoundation.org




I was just teasing when I mentioned IAccessible3... 
I think deprecating IAccessible2 would be really confusing to everyone, no 
matter what the new interface's name is. 

Perhaps something like this might be a bit less wild? 
- deprecate IAccessible2::nRelations, relation, relations 
- add IAccessibleRelationships which has only 2 methods: relations and 
relationsForType 
(although I guess then AT's would have to QI or QS to get an object's 
relations, which is more work for a pretty common thing...) 

The simplest thing to do for now is just deprecate IAccessible2::relation 
because it really is a problem (and nRelations too, because it wouldn't be 
needed without relation?) and everybody only uses IAccessible2::relations. 

Realistically, how many relations does any object have? I honestly don't 
have a feel for it... can it be quite a lot? 

Carolyn 


From: 
Pete Brunet <pete at a11ysoft.com> 
To: 
IA2 List <Accessibility-ia2 at lists.freestandards.org> 
Date: 
22/10/2009 10:27 AM 
Subject: 
[Accessibility-ia2] Relations 
Sent by: 
accessibility-ia2-bounces at lists.linuxfoundation.org




Over the last year or so there have been several posts pointing out the 
shortcomings of IA2::relation(s).  I think this is serious enough that I'd 
like to get this fixed at some convenient point.  We'd have to deprecate 
IAccessible2 and add IAccessible22 (or IAccessible2_2 if you'd prefer). 

Please send me you input either on the list or in a private email 
regarding the best time for adding the new interface.  I'd like to add it 
as an additional interface for the IA2 v2 IDL (which was recently updated 
to add IATable2 and IATableCell), but let me know if that would be a 
problem.

Is this what is needed?

Remove: nRelations, relation, relations

Add:
HRESULT relation ([in] BSTR *relationType, [out, retval] 
IAccessibleRelation **relation)

-- 
Pete Brunet
                                                                
a11ysoft - Accessibility Architecture and Development
(512) 238-6967 (work), (512) 689-4155 (cell)
Skype: pete.brunet
IM: ptbrunet (AOL, Google), ptbrunet at live.com (MSN)
http://www.a11ysoft.com/about/
Ionosphere: WS4G _______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2 at lists.linuxfoundation.org
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2

_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2 at lists.linuxfoundation.org
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/accessibility-ia2/attachments/20091022/05fd6d4d/attachment.htm