*whoosh* right over my head..
Man, I don't know how people are picking up a book and coding iPhone apps within a week...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS Should I start with basic Mac Cocoa programming?
- Thread starter CaptSaltyJack
- Start date
- Sort by reaction score
*whoosh* right over my head..
Man, I don't know how people are picking up a book and coding iPhone apps within a week...
*whoosh* right over my head..
Man, I don't know how people are picking up a book and coding iPhone apps within a week...
What other languages do you know? I might be able to explain it in the context of those languages so you get away from the Objective C confusion and can focus on the concept.
I know C, but just command line (no GUI). I know PHP. I also know C#.NET, but that's ridiculously quick and easy to build apps. I just wish Xcode/Cocoa was as "rapid app" as C#.NET
I know C, but just command line (no GUI). I know PHP. I also know C#.NET, but that's ridiculously quick and easy to build apps. I just wish Xcode/Cocoa was as "rapid app" as C#.NET
Once you get used to it it's actually pretty fast. I find it much nicer than C# (and I've been doing .NET since beta including writing a bunch of stuff to dynamically generate IL). In C# say you have a class and one of the members of the class is an interface that you're going to call to do things for you. The interface is basically like what the "files owner" is in IB. Once you attach an object that implements that interface to the class, the class can do whatever it needs to with that object. That's what the framework does when you load the view (it attaches your implementing object to the interface). Just like with your class that has the interface, if you change the object that's implementing the interface you can have different things happen or different sets of data.
Hopefully that helped and didn't confuse you further
. That's not exactly how it works in obj-c but it should give you the general concept. Anyway, I'm tired so I probably don't make enough sense right now I bought the book and stopped around the same point. It got a bit too complicated for me, like I could learn it and do copy and paste but I didn't think it would stick in my head. I decided to jump right into iphone sdk after that point, but that got me no where. Now I'm back to square one, waiting for the nda to lift and some books to show up.
I understand object c, but I feel like it doesn't really help. It's more about understanding how to use interface builder and linking it with the iphone sdk. I feel there are too many ways to something. It almost feels like php.
I gave chapter 8 another chance, another read-through. Made sure I had plenty of sleep. I think I got it now. It's just one of those things you have to drill into your head and do it over again, and maybe draw a diagram of your classes and vars/methods, and figure out what's going on.
Heck, I'll probably go through chapters 7 and 8 again, as that's where things start to get a little complicated for me.
I think I got it now. It's just one of those things you have to drill into your head and do it over again, and maybe draw a diagram of your classes and vars/methods, and figure out what's going on.Heck, I'll probably go through chapters 7 and 8 again, as that's where things start to get a little complicated for me.
I'm pretty new to all this as well, but I believe all of the binding tools in IB for Mac applications is not available for iPhone applications. In fact the Bindings inspector is not even there. So a lot of chapter 8 would be unusable on the iPhone.
It took me awhile to figure out what was going on in IB and it's relationship to the code I was writing. It all seemed rather magical like VB, blahh! I also have been doing .Net programming since version 1 of the framework and when you build UI's in Visual Studio it would actually create/modify code for you. IB is not like this (which is actually quite fortunate, Visual Studio 2003 would sometimes completely screw up your code), IB appears to simply set properties for classes that get instantiated when your application is running. So you create a View in IB and change all those values in the inspectors, when your application runs a class is instantiated and all those properties you set are applied to the new object. If you want a custom class to be hooked up to your View in IB you simply created one and set the Class name in the appropriate inspector field. Same goes for the controller.
The First Responder has something to do with keyboard events or something like that, I've not really had to mess with that at all so I'm a little fuzzy about it's use. All the ctrl+dragging that occurs is simply linking variables for objects, such as dragging a controller onto a view to set the controller's view property. You can create variables in your classes that can reference controls in your interface. So if you have a text field that you want to manipulate in code you would create a variable in your view or controller class like this:
IBOutlet UITextField *textField;
Then from IB you would be able to ctrl+drag your view onto the text field.
A delegate is like a reference to a C# interface. Some delegates require a specific protocol be implemented. A Protocol is very similar to an interface definition in C# but not all of it's methods are always required. I think I read somewhere that delegates were created as a way of extending a class through composition as opposed to subclassing.
Like I said, I'm pretty new to this as well. Some of it still seems foreign to me but once you start getting used to it you'll see the patterns and it will start to make more sense. Hopefully I didn't confuse you even more Apple really has made some cool APIs though. I just started messing around with the CoreAnimation stuff, it's very cool.
It took me awhile to figure out what was going on in IB and it's relationship to the code I was writing. It all seemed rather magical like VB, blahh! I also have been doing .Net programming since version 1 of the framework and when you build UI's in Visual Studio it would actually create/modify code for you. IB is not like this (which is actually quite fortunate, Visual Studio 2003 would sometimes completely screw up your code), IB appears to simply set properties for classes that get instantiated when your application is running. So you create a View in IB and change all those values in the inspectors, when your application runs a class is instantiated and all those properties you set are applied to the new object. If you want a custom class to be hooked up to your View in IB you simply created one and set the Class name in the appropriate inspector field. Same goes for the controller.
The First Responder has something to do with keyboard events or something like that, I've not really had to mess with that at all so I'm a little fuzzy about it's use. All the ctrl+dragging that occurs is simply linking variables for objects, such as dragging a controller onto a view to set the controller's view property. You can create variables in your classes that can reference controls in your interface. So if you have a text field that you want to manipulate in code you would create a variable in your view or controller class like this:
IBOutlet UITextField *textField;
Then from IB you would be able to ctrl+drag your view onto the text field.
A delegate is like a reference to a C# interface. Some delegates require a specific protocol be implemented. A Protocol is very similar to an interface definition in C# but not all of it's methods are always required. I think I read somewhere that delegates were created as a way of extending a class through composition as opposed to subclassing.
Like I said, I'm pretty new to this as well. Some of it still seems foreign to me but once you start getting used to it you'll see the patterns and it will start to make more sense. Hopefully I didn't confuse you even more
Apple really has made some cool APIs though. I just started messing around with the CoreAnimation stuff, it's very cool.Very pleased to have found you all
Yup! I am not alone.
I am in fact impressed by the fact that most of you guys have exactly the same questions and impressions I have been suffering from the past two weeks. Hence, I will not ask the same questions again.
I already bought the Objective C Book. I have read 80% of it and I am to the point where I do not think it will help any more. So Now I read about the Cocoa for MAC OS X book, but OSX Cocoa is clearly not the same as Cocoa Touch (or Iphone stuff). I read mixed reviews on how useful the book will be. What the heck, I'll buy it anyway, first thing in the morning tomorrow.
So here is the question. I have seen video tutorials for the IPHONE dated to march 2008, when the SDK was first released but with no Interface Builder. Hence, it was all about quite a lot of typing like in the old MS Visual C days.
I feel very good at programming on VB6 and BCB environments, which I can see IB will not be like. So... Is there like a video training out there of the steps that I need to take in order to link an outlet (or whatever it is that needs linking) to a class (or whatever the first whatever is linked to)? I have read a lot of stuff here, but unfortunately I am a VISUAL guy (which must be why I do so well with the Visual Object Oriented stuff).
Whatever the case, I know that together we will figure it out. Thanks for your input.
Best regards,
Mega-NOOBIE as of 7/29/08
Yup! I am not alone.
I am in fact impressed by the fact that most of you guys have exactly the same questions and impressions I have been suffering from the past two weeks. Hence, I will not ask the same questions again.
I already bought the Objective C Book. I have read 80% of it and I am to the point where I do not think it will help any more. So Now I read about the Cocoa for MAC OS X book, but OSX Cocoa is clearly not the same as Cocoa Touch (or Iphone stuff). I read mixed reviews on how useful the book will be. What the heck, I'll buy it anyway, first thing in the morning tomorrow.
So here is the question. I have seen video tutorials for the IPHONE dated to march 2008, when the SDK was first released but with no Interface Builder. Hence, it was all about quite a lot of typing like in the old MS Visual C days.
I feel very good at programming on VB6 and BCB environments, which I can see IB will not be like. So... Is there like a video training out there of the steps that I need to take in order to link an outlet (or whatever it is that needs linking) to a class (or whatever the first whatever is linked to)? I have read a lot of stuff here, but unfortunately I am a VISUAL guy (which must be why I do so well with the Visual Object Oriented stuff).
Whatever the case, I know that together we will figure it out. Thanks for your input.
Best regards,
Mega-NOOBIE as of 7/29/08