Harry, I know that this post is kind of old , but it doesn't look like you ever got an answer, and I think I can help.
First of all, you can read the output of your command line program in the debug console. In the source group, move the vo cursor until you here it say "debug" and interact with it. Then move vo until you hear "debug console". As far as learning programming goes, it sounds like you have the right approach. Learn the basic mechanics and program structures such as loops, functions, pointers, etc. Then start learning about object oriented programming. There are lots of different oop languages out there and they all have their own syntax, but the most important thing to focus on is the concepts of oop. It certainly takes a lot of practice, but I think that you will find that it is easier than you think. You can use interface builder with vo to design an interface, but I wouldn't recommend you do much with that until you are very comfortable with oop concepts. Hope that helped. Harry Hogue wrote: > Hello, guys, > > First, I am completely new to programming, and I've heard that it is best to > start with learning C programming and then move to Objective C which is what > is used for OSX and IOS. I have downloaded Xcode 4.5.2, I think it is, and > was wondering if there are any general suggestions for using it with > VoiceOver. Since much of the interface is dragging and dropping, my instinct > says that coding instead would be the more logical, if time-consuming choice. > In this way, the programmer would have a better idea of exactly where on the > screen things appear, etc. > > Since I am completely new to programming, I would like to get started in a > way that is helpful. I have looked at C programming tutorials, but when I > try and test the command line tool template program @HelloWorld,@ I get the > message, @Build Succeeded@ but nothing else from VoiceOver. Something tells > me the message appeared and then went away, as it is supposed to, but > VoiceOver never read it. For purposes of playing with code and testing my > code, how should I approach this_ is there a certain file(s) I should be > inputting code into as I read tutorials online, and a certain way to test > them or a place to test them with VoiceOver so they will be read by VoiceOver_ > > Again, I am just wanting to play around with the basics, here. it fascinates > me. I have no plans for creating much of anything -- programming takes years > and years of practice, and, more importantly, errors and learning how to redo > code and debugging to get it right. > > Thanks for any pointers, guys. > > Harry -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionaries@googlegroups.com. To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
