Re: Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date
Hi, On Mon, Oct 15, 2012 at 08:46:17AM -0700, V Stuart Foote wrote: Hope the fix is a simple as that! Since I reopened the FDO#53474 https://bugs.freedesktop.org/show_bug.cgi?id=53474 bug, I am happy to re-test, but I'm not set up to build. Assume I would grab the below 3.6 build on next cycle. It doesn't look as if the Master for Windows Tinderbox is being routinely built. It seems that W2008R2 tinderbox is producing builds again: see http://dev-builds.libreoffice.org/daily/W2008R2@16-minimal_build/master/2012-10-18_10.09.04/ . I am not sure the msi is installable, though, because of https://bugs.freedesktop.org/show_bug.cgi?id=55290 . The build incorporates my attempt to fix the problem, but I have not got a word back yet... D. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date
Hi, On Tue, Oct 16, 2012 at 06:23:01PM -0700, V Stuart Foote wrote: David, Nominated the fdo#53474 as a most annoying for 3.6. It is a regression from 3.5 and has been with us now for four build/QA reviews. Not sure of the etiquette but are you willing to take assignment of the bug? Provisionally, on the condition that the patch really fixes the problem :-) I am going to step back immediately if it does not, because I do not have Windows, so I have no means to debug it. The Java Accessibility testers (JavaMonkey and JavaFerret) are pretty simplistic, but appear on a par to the Accerciser test tool for Gnome ATK AT-SPI--not sure why they would not have be invoked in QA process. Unfortunately, with both the MSVC and MinGW Tinderbox builds of Master not currently producing usable builds no way to test your patch. Any chance of getting a nod from fellow devs to push down to a 3.6 build and come at it that way? I guess that would not be a problem (except to actually round someone to review the patch, because nearly everyone is at the conference). D. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date
David, Grabbed the build, and unfortunately it still has the MSI installer Error 1935 ( fdo#55290 ) https://bugs.freedesktop.org/show_bug.cgi?id=55290 affecting it. But, in reading the build info and the Tinderbox Wiki http://wiki.documentfoundation.org/Development/Tinderbox the number 16 TB is a minimal build and does not have support for Java--so would not be a good test platform for the Java Access Bridge -- Accessibility role mappings. Looking at the Wiki and the Tinderbox Status - MASTER http://tinderbox.libreoffice.org/MASTER/status.html listing, expect will need TB 6 (MSVC) or possibly even the TB 7 (MinGW) back on-line. Stuart -- View this message in context: http://nabble.documentfoundation.org/RE-libreoffice-accessibility-Latest-Libo-Won-t-Play-Nice-with-myJRE-tp4012436p4014319.html Sent from the Dev mailing list archive at Nabble.com. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date
David, Nominated the fdo#53474 as a most annoying for 3.6. It is a regression from 3.5 and has been with us now for four build/QA reviews. Not sure of the etiquette but are you willing to take assignment of the bug? The Java Accessibility testers (JavaMonkey and JavaFerret) are pretty simplistic, but appear on a par to the Accerciser test tool for Gnome ATK AT-SPI--not sure why they would not have be invoked in QA process. Unfortunately, with both the MSVC and MinGW Tinderbox builds of Master not currently producing usable builds no way to test your patch. Any chance of getting a nod from fellow devs to push down to a 3.6 build and come at it that way? Stuart -- View this message in context: http://nabble.documentfoundation.org/RE-libreoffice-accessibility-Latest-Libo-Won-t-Play-Nice-with-myJRE-tp4012436p4013851.html Sent from the Dev mailing list archive at Nabble.com. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date
Hope the fix is a simple as that! Since I reopened the FDO#53474 https://bugs.freedesktop.org/show_bug.cgi?id=53474 bug, I am happy to re-test, but I'm not set up to build. Assume I would grab the below 3.6 build on next cycle. It doesn't look as if the Master for Windows Tinderbox is being routinely built. Build Info tinderbox: administrator: fridrich.st...@bluewin.ch tinderbox: buildname: Win-x86_9-Voreppe tinderbox: tree: libreoffice-3-6 tinderbox: pull time 2012-10-15 09:16:07 http://dev-builds.libreoffice.org/daily/Win-x86_9-Voreppe/libreoffice-3-6/ If there is a better build for testing, please let me know. Stuart -- View this message in context: http://nabble.documentfoundation.org/RE-libreoffice-accessibility-Latest-Libo-Won-t-Play-Nice-with-myJRE-tp4012436p4013526.html Sent from the Dev mailing list archive at Nabble.com. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date
V Stuart Foote wrote It doesn't look as if the Master for Windows Tinderbox is being routinely built. That should have read ... is building to completion without errors. -- View this message in context: http://nabble.documentfoundation.org/RE-libreoffice-accessibility-Latest-Libo-Won-t-Play-Nice-with-myJRE-tp4012436p4013533.html Sent from the Dev mailing list archive at Nabble.com. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [libreoffice-accessibility] Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date
Hello, No apology needed Stuart. You have done more than most and i would like to take this opportunity to thank you on list. I new the lo was not write but I now am pleased that someone from lo is now agreeing with me. anyway moving on I will take a look at the link to vote on the ticket to get accessibleIa2 added into the code for lo, let me once again thank you for all your effort and hard work on this. OK we don't have the result we would like but now we know we can maybe try and get a fix for it. On 15/10/2012 01:10, V Stuart Foote wrote: LibreOffice versions 3.6.0 and later have not correctly implemented the Java Access Bridge (JAB) modules used to expose the Java Accessibility API roles for Windows users. It took me a little while to work out the testing methods, but the Oracle test utilities JavaFerret-32 and JavaMonkey-32 show that LibreOffice is not implementing the Java Accessibility API and therefore does not expose accessibility roles to Assistive Technologies. Neither JAB v.2.0.2 or v 2.0.3, nor current JRE version 1.6u35 or 1.7u7 will make a difference. I tested LibreOffice builds 3.6.0.4, 3.6.1.2, 3.6.2.2, and 3.6.3.1 none of which are functional. In addition today I completed testing of ALL builds of LibreOffice from 3.4.5 to 3.5.7rc2. With exception of the 3.5.0 build they all correctly map Java Accessibility API roles to UNO Accessibility roles. The Java Accessibility API is not as comprehensive as the IAccessible2 role mappings provided by IBM Lotus Symphony 3.0.1, but it is functional for the 3.4 and 3.5 releases of LibreOffice. And, for these versions Windows Assistive Technologies will work. For example, the Windows NVDA screen reader will function with cursor control and component announcements for the entire document tree. Windows versions of LibreOffice 3.6, including the current build 3.6.3 rc1, are NOT USEABLE with Assistive Technologies and they have not been usable with Windows Assistive Technologies at any point. For folks that I've mislead with my insistence that all is well with LibreOffice 3.6 and Java Access Bridge and JRE with use of Assistive Technologies like NVDA screen reader I was wrong--I apologize. I've updated the FDO#53474 (http: bug report https://bugs.freedesktop.org/show_bug.cgi?id=53474 ) and would encourage folks to vote, i.e. comment on, the enhancement to implement IAccessible2 API ( http://wiki.documentfoundation.org/Vote_for_Enhancement ) for Windows builds by incorporating the IBM contributed Symphony code base as a replacement of the Java Accessibility API as that is probably the fastest means of bringing Windows builds of LibreOffice to the same functional level as Linux builds that use the ATK AT-SPI accessibility APIs. Stuart ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [libreoffice-accessibility] Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date
Hi :) +1 A huge +1 really. Just +1 doesn't really get close! Definitely impressive work from Stuart there! Above and beyond gets closer. I tried voting but found that really unclear, and i have been editing wiki's for a while now. I was able to add a comment in support but i'm not sure if it's the type of thing they are looking for. Stuart also gave links to the relevant bug-reports and i have a feeling it might be easier to post comments there but only if they help the devs get closer to fixing the problems, such as version number of LO you are using and which OS (Windows Xp, Ubuntu or whatever) I think the wiki wanted more conversational type comments but i wasn't sure what i should say. Regards from Tom :) --- On Mon, 15/10/12, Kevin Cussick the.big.white.sheph...@googlemail.com wrote: From: Kevin Cussick the.big.white.sheph...@googlemail.com Subject: Re: [libreoffice-accessibility] Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date To: V Stuart Foote vstuart.fo...@utsa.edu Cc: accessibil...@global.libreoffice.org, libreoffice@lists.freedesktop.org, us...@glogal.libreoffice.org Date: Monday, 15 October, 2012, 20:04 Hello, No apology needed Stuart. You have done more than most and i would like to take this opportunity to thank you on list. I knew the LO was not right but I now am pleased that someone from LO is now agreeing with me. Anyway. moving on, I will take a look at the link to vote on the ticket to get accessibleIa2 added into the code for LO. Let me once again thank you for all your effort and hard work on this. OK we don't have the result we would like but now we know we can maybe try and get a fix for it. On 15/10/2012 01:10, V Stuart Foote wrote: LibreOffice versions 3.6.0 and later have not correctly implemented the Java Access Bridge (JAB) modules used to expose the Java Accessibility API roles for Windows users. It took me a little while to work out the testing methods, but the Oracle test utilities JavaFerret-32 and JavaMonkey-32 show that LibreOffice is not implementing the Java Accessibility API and therefore does not expose accessibility roles to Assistive Technologies. Neither JAB v.2.0.2 or v 2.0.3, nor current JRE version 1.6u35 or 1.7u7 will make a difference. I tested LibreOffice builds 3.6.0.4, 3.6.1.2, 3.6.2.2, and 3.6.3.1 none of which are functional. In addition today I completed testing of ALL builds of LibreOffice from 3.4.5 to 3.5.7rc2. With exception of the 3.5.0 build they all correctly map Java Accessibility API roles to UNO Accessibility roles. The Java Accessibility API is not as comprehensive as the IAccessible2 role mappings provided by IBM Lotus Symphony 3.0.1, but it is functional for the 3.4 and 3.5 releases of LibreOffice. And, for these versions Windows Assistive Technologies will work. For example, the Windows NVDA screen reader will function with cursor control and component announcements for the entire document tree. Windows versions of LibreOffice 3.6, including the current build 3.6.3 rc1, are NOT USEABLE with Assistive Technologies and they have not been usable with Windows Assistive Technologies at any point. For folks that I've mislead with my insistence that all is well with LibreOffice 3.6 and Java Access Bridge and JRE with use of Assistive Technologies like NVDA screen reader I was wrong--I apologize. I've updated the FDO#53474 (http: bug report https://bugs.freedesktop.org/show_bug.cgi?id=53474 ) and would encourage folks to vote, i.e. comment on, the enhancement to implement IAccessible2 API ( http://wiki.documentfoundation.org/Vote_for_Enhancement ) for Windows builds by incorporating the IBM contributed Symphony code base as a replacement of the Java Accessibility API as that is probably the fastest means of bringing Windows builds of LibreOffice to the same functional level as Linux builds that use the ATK AT-SPI accessibility APIs. Stuart ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date
LibreOffice versions 3.6.0 and later have not correctly implemented the Java Access Bridge (JAB) modules used to expose the Java Accessibility API roles for Windows users. It took me a little while to work out the testing methods, but the Oracle test utilities JavaFerret-32 and JavaMonkey-32 show that LibreOffice is not implementing the Java Accessibility API and therefore does not expose accessibility roles to Assistive Technologies. Neither JAB v.2.0.2 or v 2.0.3, nor current JRE version 1.6u35 or 1.7u7 will make a difference. I tested LibreOffice builds 3.6.0.4, 3.6.1.2, 3.6.2.2, and 3.6.3.1 none of which are functional. In addition today I completed testing of ALL builds of LibreOffice from 3.4.5 to 3.5.7rc2. With exception of the 3.5.0 build they all correctly map Java Accessibility API roles to UNO Accessibility roles. The Java Accessibility API is not as comprehensive as the IAccessible2 role mappings provided by IBM Lotus Symphony 3.0.1, but it is functional for the 3.4 and 3.5 releases of LibreOffice. And, for these versions Windows Assistive Technologies will work. For example, the Windows NVDA screen reader will function with cursor control and component announcements for the entire document tree. Windows versions of LibreOffice 3.6, including the current build 3.6.3 rc1, are NOT USEABLE with Assistive Technologies and they have not been usable with Windows Assistive Technologies at any point. For folks that I've mislead with my insistence that all is well with LibreOffice 3.6 and Java Access Bridge and JRE with use of Assistive Technologies like NVDA screen reader I was wrong--I apologize. I've updated the FDO#53474 (http: bug report https://bugs.freedesktop.org/show_bug.cgi?id=53474 ) and would encourage folks to vote, i.e. comment on, the enhancement to implement IAccessible2 API ( http://wiki.documentfoundation.org/Vote_for_Enhancement ) for Windows builds by incorporating the IBM contributed Symphony code base as a replacement of the Java Accessibility API as that is probably the fastest means of bringing Windows builds of LibreOffice to the same functional level as Linux builds that use the ATK AT-SPI accessibility APIs. Stuart ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Reality Check - Windows Java Accessibility API non-functional for ALL LibreOffice 3.6.x releases to date
Hi, On Sun, Oct 14, 2012 at 07:10:35PM -0500, V Stuart Foote wrote: LibreOffice versions 3.6.0 and later have not correctly implemented the Java Access Bridge (JAB) modules used to expose the Java Accessibility API roles for Windows users. It took me a little while to work out the testing methods, but the Oracle test utilities JavaFerret-32 and JavaMonkey-32 show that LibreOffice is not implementing the Java Accessibility API and therefore does not expose accessibility roles to Assistive Technologies. Neither JAB v.2.0.2 or v 2.0.3, nor current JRE version 1.6u35 or 1.7u7 will make a difference. I tested LibreOffice builds 3.6.0.4, 3.6.1.2, 3.6.2.2, and 3.6.3.1 none of which are functional. I guess that java_uno_accessbridge.dll does not export the needed symbols after gbuildification of module accessibility, in which case commit d475a059fc9f07f4d896bd67649c7d800fc66f6f should fix the problem. Any testers/reviewers? D. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
