Hi, fellow QS developers

[Etienne Samson]

Hi !

I finally got the time to beg Alcor for the admin password for this
group. I was (happily) surprised to see 40 people waiting for
admission on this list ;-). Make yourself at home, I'll try to post
some more development news in a few weeks.

Etienne

[Nicholas Jitkoff]

And apologies to all for being so terribly delayed in getting you
approved. Up till now there wasn't much development news, but I look
forward to seeing what you all discuss.

Nicholas

[Patrick]

Cheers Nicholas,

I guess we can now start discussing where we want QS to go!

[Rich Simpson]

Hi everyone,

I originally asked to be on this list because I'm very interested in
using QS to increase the accessibility of OS X. One of my graduate
students was able to modify QS to work with VoiceOver (to a degree)
with very few changes to the underlying code, in spite of the fact
that he was new to programming on the Mac and neither of us was
particularly familiar with the QS code. I think QS could be extremely
useful if more of the accessibility hooks were embedded in the QS code.

rich

[Nicholas Jitkoff]

what other hooks are you interested in?

[Andrew Eberbach]

Hi,

Maybe this isn't the right place for this but I think that setting up
search engine searches should be made a lot easier. Maybe even have a
function that pulls in search engines from firefox...
thoughts?

-andrew

[Rich Simpson]

We worked exclusively with the Bezel interface, and were able to get
VoiceOver to announce the text within the application, action and
object buttons by adding this function to QSObjectCell:

(void)accessEnableQS:(NSString *)accName {
[self setTitle:accName];

NSAccessibilityPostNotification(self,
NSAccessibilityFocusedWindowChangedNotification);

}

We then edited the drawSearchPlaceholderWithFrame() method by adding
the following function call at the end:

[selfaccessEnableQS:defaultText];

and edited the drawTextForObject() method by adding the following
function call at the end:

[selfaccessEnableQS:nameString];

These changes made the text of the buttons available to VoiceOver, but
do not work with the list items underneath each button. There are
also ways to "link" two controls, so that VoiceOver knows that a
button is directly related to a list. Since QS is built using Cocoa,
it should be easy to add in the necessary accessibility attributes
where the text for buttons and list items are set.

Perhaps the place to start is a list of the methods where button or
list text is set or changed.

rich