Apple

On 1/23/13, Brian Syme <email@hidden> wrote:
> Xcode has a pretty complex and fiddly interface even when you can see it.
> Navigating your way around it with voiceover is tough, but I assume you're
> a lot more comfortable with voiceover than I am.

Probably, but it isn't bad once you get the hang of it, and your
knowledge of a relatively complex topic like interaction (see below)
is impressive for someone who does not need VO. I'm just glad when
developers know what VO is so they can test to be sure their apps are
accessible.

>
> Do you have a good idea of the overall layout of the Xcode interface?
> Basically the Xcode window contains multiple panes. On the left you have
> the "Navigator" pane, in the center there's an "Editor" pane and on the
> right there's a "Utilities" pane.

I think what you call the Editor pane VO calls the Source Code Group
(yep, even when there's no source code to be found). Thinking of it as
a more general editor area makes more sense though, I'll have to
remember that.

>
> Each pane has several modes it can be in. What you select in the left hand
> navigator pane can affect what's displayed in the central editor pane, and
> what you select in the central editor pane can affect what you see in the
> right hand utilities pane.

Yes, I'd found this out, but I always get caught up in the source code
group (editor pane) and I sometimes forget to check my navigator
settings. This may well be the problem.

>
> I think there are two reasons why you can't see the code for your view:
> 1. Navigating to the editor pane with voiceover is tricky.

I've gotten used to it, you just have to stop interacting
(ctrl-option-shift-up) until you are at the top level of the window.

> 2. There actually isn't any source code associated with the view yet.

Well, that certainly would explain a lot! :)

>
> I think you may be trapped in the left hand navigator pane. Try getting to
> the top of the navigator group (shift+control+option+up a few times) then
> using voiceover's regular navigation (i.e. just control+option and cursor
> keys) to find the editor pane.
>
> Hopefully that gets you a bit further. As far as getting code associated
> with a view is concerned, basically you're going to create a new class
> (File+New+File menu options) that derives from NSView. Then you're going to
> use the Identity Inspector in the right hand utility pane to change its
> class from the default NSView to whatever your new class is called.

I thought I'd automatically have a view? I should have said that I
selected the Cocoa template when I made the project, so I have the
standard menus and their items, plus the very basic window with the
default controls in it. Given that (sorry I didn't mention it in my
first post), will I still have to make a new class?

>
> Like I say, this is all pretty fiddly when you can see all these modal UI
> changes happening, so I'm not surprised you've had a tough time figuring it
> out.
>
> Maybe there's a guide to xcode for blind users on the web already?

I wish. In fact, that's part of why I'm doing this, so I can get
everything figured out and then write up such a guide. A big part is
the inaccessibility of Interface Builder, but that's another thread
(and support call, and bug report). Thanks for your response.

>
> Brian
>
>
> On Wed, Jan 23, 2013 at 6:58 AM, Alex Hall <email@hidden> wrote:
>
>> Hello all,
>> I am pretty new to Xcode and Objective-c, so sorry that this is such a
>> basic question: how do I get to the files I want or create new ones? I
>> must
>> also say that I am blind, relying on Voiceover (Apple's built-in screen
>> reader), so keyboard commands or menu items are the only way I can access
>> Xcode. Voiceover can move the mouse pointer to the object Voiceover is
>> on,
>> and then click or even drag (though dragging is sort of hit-or-miss) but
>> that's all I can do with a mouse.
>>
>> Anyway, what I want to do is play around with capturing keyboard input
>> directly in my window. So I want to set my view as the first responder
>> and
>> then override the keyUp, and maybe some other, events used in NSResponder
>> (from which NSView inherits). Here's the problem: I can't find the actual
>> code where the NSView instance is instantiated. Actually, I can't find
>> any
>> code at all. I have a table inside the mainMenu.xib group (itself in the
>> Source Code group), and this table has appDelegate and all my UI stuff,
>> but
>> I can't seem to show the code at all. Yes, I can go view and edit the
>> files
>> in Finder, but it seems like I should be able to edit code in Xcode... I
>> realize my terms might be confusing, since I am coming at this only able
>> to
>> relate how Voiceover organizes and labels the different elements of the
>> screen, so let me know if I am not making sense and I'll see what I can
>> do
>> to explain this differently. Thanks in advance for any help.
>>
>>
>> Have a great day,
>> Alex (msg sent from Mac Mini)
>> email@hidden
>>
>>
>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Xcode-users mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>>
>

--
Have a great day,
Alex (msg sent from GMail website)
email@hidden