Re: [Accessibility-ia2] IAccessible2_2 inherits from IAccessible

2012-09-10 Thread James Teh

Hi Pete and all,

I can't remember whether this has been covered before, but I think 
completely replacing IAccessible2 with IAccessible2_2 rather than just 
extending will make life very difficult for both AT and app developers 
alike. I understand that it'd be nice to clean up IAccessible2 by 
removing deprecated methods and parameters. However, the reality is that 
IAccessible2_2 isn't going to be implemented by every vendor overnight 
and we will still need to deal with IAccessible2 in older versions of 
apps even if/once it is. With the current IAccessible2_2 approach, every 
vendor will have to implement all of the duplicated methods twice, once 
for IAccessible2 and once for IAccessible2_2. It essentially has to be 
treated as a new API even though most of the methods are the same.


The deprecated methods in IAccessible2 obviously still need to be marked 
as deprecated. I think IAccessible2_2 should just contain the new 
methods. Whether it inherits from IAccessible2 is an open question and 
doesn't matter as much. I think this would make sense, but I'm happy 
either way.


Thoughts?

Jamie

On 8/09/2012 10:43 AM, Pete Brunet wrote:

I am creating IAccessible2_2 to make some changes:
- add accessibleWithCaret
- add relationTargetsOfType
- remove nRelations/relation/relations
- add attribute // return object attribute by name
- remove unused [in] parameter on extendedStates and localizedExtendedStates

I could also change this to remove the unneeded inheritance from
IAccessible, but that might cause too much work for those reworking code
from IAccessible2.  Is that true?

Pete
--
*Pete Brunet*

a11ysoft - Accessibility Architecture and Development
(512) 467-4706 (work), (512) 689-4155 (cell)
Skype: pete.brunet
IM: ptbrunet (AOL, Google), ptbru...@live.com (MSN)
http://www.a11ysoft.com/about/
Ionosphere: WS4G


___
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2



--
James Teh
Director, NV Access Limited
Email: ja...@nvaccess.org
Web site: http://www.nvaccess.org/
Phone: +61 7 5667 8372
___
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2


Re: [Accessibility-ia2] ia2_api_all.idl

2012-09-10 Thread James Teh

Hi Pete,

Unfortunately, I don't think this is a good idea. Many apps and ATs will 
still need to support the old interfaces for quite some time, so having 
them excluded from the merged IDL isn't an option.


Thanks,
Jamie

On 11/09/2012 1:39 AM, Pete Brunet wrote:

I was getting some errors when using ia2_api_all.idl (the merged API
file) and to fix it I removed all the IDL files that have been
deprecated, i.e. IA2, IATable, IAText, and IAHypertext which have been
replaced with IA2_2, IATable2, IAText2, and IAHypertext2.  Is that OK?
With some more work I'm sure I could fix this if it's a problem but I
don't want to spend the time if those old IDL files aren't needed in the
merged IDL file.

Pete
--
*Pete Brunet*

a11ysoft - Accessibility Architecture and Development
(512) 467-4706 (work), (512) 689-4155 (cell)
Skype: pete.brunet
IM: ptbrunet (AOL, Google), ptbru...@live.com (MSN)
http://www.a11ysoft.com/about/
Ionosphere: WS4G


___
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2



--
James Teh
Director, NV Access Limited
Email: ja...@nvaccess.org
Web site: http://www.nvaccess.org/
Phone: +61 7 5667 8372
___
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2


[Accessibility-ia2] ia2_api_all.idl

2012-09-10 Thread Pete Brunet
I was getting some errors when using ia2_api_all.idl (the merged API
file) and to fix it I removed all the IDL files that have been
deprecated, i.e. IA2, IATable, IAText, and IAHypertext which have been
replaced with IA2_2, IATable2, IAText2, and IAHypertext2.  Is that OK? 
With some more work I'm sure I could fix this if it's a problem but I
don't want to spend the time if those old IDL files aren't needed in the
merged IDL file.

Pete
-- 
*Pete Brunet*

a11ysoft - Accessibility Architecture and Development
(512) 467-4706 (work), (512) 689-4155 (cell)
Skype: pete.brunet
IM: ptbrunet (AOL, Google), ptbru...@live.com (MSN)
http://www.a11ysoft.com/about/
Ionosphere: WS4G
___
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2


Re: [Accessibility-ia2] Getting the document accessible

2012-09-10 Thread Pete Brunet
The new IDL for version 1.3 is pretty much ready to go.  The only thing
I haven't done is to add the 4 relations:

IA2_RELATION_CONTAINING_DOCUMENT
IA2_RELATION_CONTAINING_TAB
IA2_RELATION_CONTAINING_WINDOW
IA2_RELATION_CONTAINING_APPLICATION

Is there an issue with plugin container or can that be handled via
getting the parent?

Pete

On 9/9/12 3:13 AM, James Teh wrote:
> On 8/09/2012 10:14 AM, Alexander Surkov wrote:
>> We had an issue with plugins (find a plugin container from plugin) but
>> new relation might not be a fix here. Jamie?
> I don't believe a new relation is the correct solution. The plugin
> container really should be the parent of the plugin.
>
> Jamie
___
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2