Re: Top-10 Accessibility API Wish List
Re: Top-10 Accessibility API Wish List
- Subject: Re: Top-10 Accessibility API Wish List
- From: Michael Kamprath <email@hidden>
- Date: Wed, 11 Sep 2002 22:57:01 -0700
on 9/11/02 12:22 PM, Guy Fullerton at email@hidden wrote:
>
> As of now, my top requests for the API are as follows:
>
>
>
> 1. Parity between Cocoa and Carbon window UI elements
>
>
You mention several specific differences. Please make sure each of these
>
(and any others you find) is accompanied by a bug.
>
How specific would you want me to get with my differences. I've already
filed two bugs for two of the differences (#3043018 and #3043011), but if
you want me to enumerate all of the differences, that would get quite
excessive. Can't the general request of "parity between Cocoa and Carbon"
applications stand on its own?
>
> This includes the ability to close a
>
> window by "pressing" the window's close box UI element.
>
>
We already have a bug to cover this.
>
>
That said, we are still trying to figure out exactly how well we can
>
physically support it, as well as whether we even want to do so for certain
>
applications. CarbonEvent-based windows can be given this functionality
>
easily. Unfortunately, non-CarbonEvent-based windows must be "puppet
>
stringed" (read: "tricked") into thinking there was a mouse down in the
>
close box.
>
Just out of curiosity, OS X has Cocoa and Carbon API's, and WNE-based apps
are really Carbon Event apps layered on top of the Carbon Event model. I'm
going to assume Classic apps are what you are talking about as "non-Carbon
Event" windows, or is there are third type of application (Java Swing???)
that aren't Cocoa-based or can't understand Carbon Events?
>
Though it is a solvable problem for most apps, "puppet stringing" is complex
>
and, well, rather gross. We're not convinced that we want to puppet string
>
non-CarbonEvent-based apps into having richer Accessibility support. In
>
addition, there will be some applications that simply don't respond to
>
puppet stringing.
I can understand there must be a line drawn somewhere, my complaint has to
do with I don't think that line has been pushed as far as it reasonably can
go. It certainly would not be disappointing if Classic applications we not
supported by Accessibility - after all, Classic is dead, right? - but Carbon
Event application really should be fully supported. And that is exactly what
my request is (no more).
Michael F. Kamprath
email@hidden
Keyboard Maestro - Conduct Your Mac Like a Pro!
Download a free copy today at: www.KeyboardMaestro.com
_______________________________________________
accessibility-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/accessibility-dev
Do not post admin requests to the list. They will be ignored.