Re: thoughts about voiceover and its usage of the accessibility API

2015-06-23 Thread Sabahattin Gucukoglu
On 23 Jun 2015, at 13:38, Jason White wrote: > Sabahattin Gucukoglu wrote: >> I dunno what the situation >> is on Linux nowadays, but last I looked it was all still GNOME and QT hadn’t >> yet made their bridge. Is that still true? > > No. QT made their bridge directly to the AT-SPI layer, which

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-23 Thread Jason White
Sabahattin Gucukoglu wrote: > I dunno what the situation > is on Linux nowadays, but last I looked it was all still GNOME and QT hadn’t > yet made their bridge. Is that still true? No. QT made their bridge directly to the AT-SPI layer, which uses DBus for inter-process communication. That is, QT

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-22 Thread Sabahattin Gucukoglu
Yes, Swift was my thought as well, assuming of course that people adopt it. Maybe indirectly we will get more interop as people start targeting the runtime via Swift or learn the details from the compiler. It’s not clear how much of the language will be open-sourced, but since Apple wants to s

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-22 Thread 'Chris Blouch' via MacVisionaries
I wonder if this will change with Swift being open source. From what I hear developers really like it, other than all the usual "just outta beta" kind of quirks. Seems like there has been this Apple Way of developing even back in the Orca Pascal days. Most of the dev work wasn't writing code in

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-22 Thread Sabahattin Gucukoglu
My primary objection to the Apple accessibility approach is its complete Cocoa, language and runtime oligarchy. You have to use the Objective-C runtime to interact with the accessibility “Protocol” and Apple doesn’t seem very interested in allowing or supporting any kind of access to that runti

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-22 Thread Yuma Decaux
Hi shawn, Try UI browser which checks every UI component in your interface for any information it can extract, in arrays of values that work similarly to a collection in a json or hive table (this is the closest I can illustrate it to be though it probablhy does not adopt the same API). This ca

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-22 Thread Sean Murphy
Hello, do you have any more info on what you have outlined below? since this is an area of interest for myself. Any pointers would be helpful and grateful. Sean > On 22 Jun 2015, at 3:27 am, Yuma Decaux wrote: > > The current OS has python, applescript and jscript that can send information

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-21 Thread Jason White
Yuma Decaux wrote: > I’m not sure what happens on the windows side, but I’ve taken it to myself > to do everything a coder would do on the mac, and so far it’s getting > smoother everytime. And much much faster too. Can’t say more. To the best of my knowledge, some Windows screen readers still

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-21 Thread Shaf
How accessible is creating a Mac/iOS app with XCode? On 6/21/2015 6:27 PM, Yuma Decaux wrote: The current OS has python, applescript and jscript that can send information directly to voice over, but I haven’t touched the scripts pertaining to these in a while as there are 3rd party application

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-21 Thread Yuma Decaux
The current OS has python, applescript and jscript that can send information directly to voice over, but I haven’t touched the scripts pertaining to these in a while as there are 3rd party applications that allow to do this very well. Also, there are a bunch of CL tools that also allow some less

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-20 Thread Sean Murphy
On either platform, a developer can use their own controls still. They do not have to use the provided objects in the Coco library or Windows development tool. This occurs equally on both platforms for the reasons that have already been raised. The struggle anyone has even if you work within the

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-20 Thread Yuma Decaux
Hi, Let me just add that the wwdc this year has put a highlight on accessibility to the developers attending or downloading the workshop videos, so saying that apple has put accessibility to the bottom of the list is untrue. In addition, now all standard UI controls in xcode are by default acce

Re: thoughts about voiceover and its usage of the accessibility API

2015-06-20 Thread Littlefield, Tyler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello: First, it's always a really hard discussion when someone with little to no development experience talks about how things "should" be done because they're usually way off. So I'll explain how things work currently. A long long time ago, in a gal