Let me start out by thanking you for your articulate response. I’m going to start by saying you’re absolutely right, http://stackoverflow.com/ is indeed a forum, now, this may not be exactly what you want to hear but to my knowledge here’s what’s up. The only reliable full documentation of all API’s, methods, toolkits etc... Is the mac and iOS dev center libraries. Here are two direct links: For mac, https://developer.apple.com/library/ios/navigation/index.html and for IOS: https://developer.apple.com/library/ios/navigation/ These are the only places i’m aware of that’ll have everything documented, the problem is the quality of the documentation. If you want something that’s comprehensive to beginners I have never seen anything i’ve been satisfied with, apple tends to deprecate all their methods every so often so any tutorial written is usually out of date. Then you’ve got the whole ARC issue (i personally love ARC, but it has some issues) (Automatic Reference Counting) for those of you who don’t know.
So in my experience a comprehensive tutorial on how to bypass the interface builder doesn’t exist. That being said it technically does exist in the apple documentation, but it’s convoluted. Let’s use the example I posted in my last reply. If you were to look up the UIButton Class Reference in the IOS library I pointed you to, you’d see a long list of methods you can call to manipulate said button, and not a single one of them would be what I used in that small code snippet. However, at the top of the page you’ll see that UIButton inherits from UIControl, UIView, UIResponder and NSObject. Now we start to see some of the methods used, initWithFrame for example is a UIView method (which I can call because UIView is a superclass of UIButton). However my addTarget: method isn’t part of UIView it’s part of UIControl (again, a superclass of UIButton). Well now we look at UIControl’s documentation and there’s addTarget: which tells us we need 2 parameters, a selector, in my example this was @selector(buttonPressed) and a Control Event, now we have to figure out what a control event is and how it’s attached so we look at the documentation on UIControlEvents and FINALLY we see this message: UIControlEventTouchUpInside A touch-up event in the control where the finger is inside the bounds of the control. Available in iOS 2.0 and later. Declared in UIControl.h Well yay, after 4 or 5 pages of various methods and superclasses we’ve finally found what we’re looking for. So I hate to just point you towards these libraries and walk away. This is where stack overflow becomes useful, I have found most questions I’ve had are answered in detail on that forum. You will notice that apple does have a couple of “programming guides” that are useful to look at, one such guide that should at least get you started on bypassing the interface builder is the “view programming guide”, you’ll see it in the libraries, since all of your UI objects have UIView as a superclass you really should take a look at it, so you can understand how to initialize an object in a specific location and then add it to your superview. I know it’s been a long (and possibly confusing) message so i’ll wrap it up here. Let me just say that it is true learning to programmatically add UI elements is a incredibly useful tool and any developer who’s going to write something more complicated than “hello world” usually initializes at least some of his/her UI elements programmatically (since it gives you so much more control). Personally I use both as needed. I hope this has been at least somewhat helpful. I’m writing this as I’m headed out the door so if anything needs clarification let me know and I’ll do my best. On Jul 5, 2013, at 8:41 AM, Paul Hunt <prhu...@att.net> wrote: > Hello Tyler. Here’s the problem. The developers who build the Interface > Builder know a lot more about Objective C and the various APIS than we do. > When people use the Interface builder, much of the heavy lifting is already > done for them. Consequently, Authors who write textbooks don’t take the time > to take us under the hood where we really need to be. Instead, they teach the > Interface builder then teach students to write the code for the events. I > checked www.overstock.com and found it to be a huge general purpose forum. We > really need access to comprehensive Objective C documentation, a complete > list of the APIS and the documentation for each. Once we learn to build > applications programmatically, then we are more competent programmers than > our sighted counterparts because we understand what’s really going on. In > addition, when we use a textbook, we literally have to translate Interface > Builder speak into lines of code. The question then is this, where is the > Objective C documentation? Where can we find a description of all of the > APIS? Can you point us in the right direction? > > Thanks so much. > > > > From: macvisionaries@googlegroups.com > [mailto:macvisionaries@googlegroups.com] On Behalf Of Tyler Thompson > Sent: Friday, July 5, 2013 2:13 AM > To: macvisionaries@googlegroups.com > Subject: Re: xcode creating actions and outlets > > believe me i understand the frustrations of working with objective C, > especially if it’s new. As it happens I find that programmatically linking > your UI elements tends to actually work a little better (as it gives you much > more control), but for each person it’s different :) > > > On Jul 5, 2013, at 1:05 AM, Yuma Antoine Decaux <jamy...@gmail.com> wrote: > > > Hi, > > There is a method which i found on the maccessibility news page. Convoluted, > and not able to do it yet, it's driving me crazy. > > I might try it programmatically but i'm going through a textbook method and > they're entirely gui based so i'm left wanting, once more. Starting to get > tired of the whole idea of computers. > > Feel like throwing this macbook out and hammer it > > > > > "Light has no value without darkness" > > > > On 5/07/2013, at 12:28 PM, Tyler Thompson <tktpianostud...@gmail.com> wrote: > > > To tack on to my previous comment here’s how you can programatically link > objects with objective c > > NSButton *theButton; > [theButton addTarget:self action:@selector(buttonMethod:) > forControlEvents:someControlEvent]; > > > On Jul 4, 2013, at 10:23 PM, Yuma Antoine Decaux <jamy...@gmail.com> wrote: > > > Hi All, > > I am going through an IOS book right now, and am stuck at a point where i > need to create an action in my controller for a button. I'm supposed to > control drag a button to my assistant editor so that x code can automatically > place the appropriate action method and properties to my project.h, project.m > and project.xib files. But there is no control drag in voice over. > > Is this another unsurmountable obstacle or is there actually a method to do > this? > > Any help greatly appreciated > > Best regards, > > Yuma > > > > "Light has no value without darkness" > > > > > "Light has no value without darkness" > > > > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to macvisionaries+unsubscr...@googlegroups.com. > To post to this group, send email to macvisionaries@googlegroups.com. > Visit this group at http://groups.google.com/group/macvisionaries. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to macvisionaries+unsubscr...@googlegroups.com. > To post to this group, send email to macvisionaries@googlegroups.com. > Visit this group at http://groups.google.com/group/macvisionaries. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to macvisionaries+unsubscr...@googlegroups.com. > To post to this group, send email to macvisionaries@googlegroups.com. > Visit this group at http://groups.google.com/group/macvisionaries. > For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To unsubscribe from this group and stop receiving emails from it, send an > email tomacvisionaries+unsubscr...@googlegroups.com. > To post to this group, send email tomacvisionar...@googlegroups.com. > Visit this group athttp://groups.google.com/group/macvisionaries. > For more options, visithttps://groups.google.com/groups/opt_out. > > > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To unsubscribe from this group and stop receiving emails from it, send an > email tomacvisionaries+unsubscr...@googlegroups.com. > To post to this group, send email tomacvisionar...@googlegroups.com. > Visit this group at http://groups.google.com/group/macvisionaries. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/groups/opt_out.
